Question

<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

Christopher Boyd · Answer

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

Christopher Boyd · Answer

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

Christopher Boyd · Answer

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

jawnsy · Answer

same user I think <https github com PrefectHQ prefect helm issues 101>

Hongbo Miao · Answer

Thanks < Anna Geller> for helping to forward here smiley Hi < Christopher Boyd> I initially think to set like this to use DNS name when deploy Prefect Orion ```orion env name PREFECT API URL value ``` 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

Hongbo Miao · Answer

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

Ryan Peden · Answer

If you want a different API URL just for the web UI you can set `PREFECT ORION UI API URL`

Hongbo Miao · Answer

Thanks Ryan I will try `PREFECT ORION UI API URL` and report back for what I found

Hongbo Miao · Answer

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

Anna Geller · Answer

thanks for sharing your solution on Discourse pray