https://prefect.io logo
Title
a

Anna Geller

01/06/2023, 8:17 PM
Here is a user question about network issue with prefect-helm - sharing here in case somehow knows how to help
:gratitude-thank-you: 1
c

Christopher Boyd

01/06/2023, 8:47 PM
so in the yaml file, he is setting the api url to localhost
👍 1
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?
j

jawnsy

01/06/2023, 9:21 PM
h

Hongbo Miao

01/06/2023, 10:12 PM
Thanks @Anna Geller for helping to forward here! 😃 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: <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? 🤔
r

Ryan Peden

01/06/2023, 11:55 PM
If you want a different API URL just for the web UI, you can set
PREFECT_ORION_UI_API_URL
:gratitude-thank-you: 1
h

Hongbo Miao

01/07/2023, 12:57 AM
Thanks Ryan, I will try
PREFECT_ORION_UI_API_URL
and report back for what I found!
👍 1
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! 😃
:gratitude-thank-you: 1
🙌 1
a

Anna Geller

02/03/2023, 2:48 PM
thanks for sharing your solution on Discourse 🙏
🙌 1