Hi folks, I’m encountering an issue while trying to run a Prefect flow on a Kubernetes pod using a work-pool. Here’s the setup and the problem I’m facing: ◦ Setup:I have configured a work-pool to connect to our Kubernetes cluster. ◦ I added the

PREFECT_API_URL

as a variable in the work-pool configuration. ◦ My Prefect worker is currently running locally. ◦ Problem:The local worker is pushing its

PREFECT_API_URL

to the new pod being created. Resulting in the pod having 2 values for the same variable. ◦ This results in the pod using the local

PREFECT_API_URL

instead of the one intended for the Kubernetes cluster. ◦ Consequently, the pod cannot communicate with the Prefect server, which is also running on a Kubernetes pod inside the same cluster. Question: How can I prevent the local worker from passing its

PREFECT_API_URL

to the new pod, ensuring that the pod uses the correct

PREFECT_API_URL

for the Kubernetes cluster? Any advice or solutions would be greatly appreciated!