Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<https://discourse.prefect.io/t/prefect-agent-in-local-failed-to-finish-the-workflow-with-prefect-orion-in-kubernetes/2133/7?u=anna_geller|Here> is a user question about network issue with prefect-helm - sharing here in case somehow knows how to help

so in the yaml file, he is setting the api url to localhost

localhost as a callback works if the jobs are in the same pod, in the same namespace, but when it spawns another pod, localhost is referring to that pod

the api url should arguably be the service name in front of the pod deployment?

same user I think: <https://github.com/PrefectHQ/prefect-helm/issues/101>

Thanks <@U02H1A95XDW> for helping to forward here! :smiley:
Hi <@U03FKQX1TH9> I initially think to set like this to use DNS name when deploy Prefect Orion
```orion:
  env:
    - name: PREFECT_API_URL
      value: <http://prefect-orion.hm-prefect.svc:4200/api>```
then if spawns the pod for job, it makes more sense to me as it can talk to Prefect Orion in another pod.
However, if I use DNS name, I will meet this issue when open the Prefect UI: <https://github.com/PrefectHQ/prefect-helm/issues/101>

Maybe Prefect helm can have one `PREFECT_API_URL` so that I can use DNS name, and provide a new URL for the web UI in the helm, to help web UI to communicate to the Prefect instance? :thinking_face:

If you want a different API URL just for the web UI, you can set `PREFECT_ORION_UI_API_URL`

Thanks Ryan, I will try `PREFECT_ORION_UI_API_URL` and report back for what I found!

Just add a follow up. I made it work. I posted at <https://discourse.prefect.io/t/prefect-agent-in-local-failed-to-finish-the-workflow-with-prefect-orion-in-kubernetes/2133/9?u=hongbo-miao>
Thanks everyone! :smiley:

thanks for sharing your solution on Discourse :pray: