Michał Augoff06/30/2022, 10:22 PM
and I’m facing some issues with the UI which seems to not be able to connect to the database (it’s empty). It’s a similar issue to this one but on k8s, not locally. The agent container communicates with the server container (API) just fine and is able to pick up flows. I’m also able to connect to the API via prefect CLI on my local machine, create work queues, deployments, trigger flows etc (which are then picked up by the k8s agent). But UI is empty and I’m not able to see/create e.g. worker queues. Any idea what I might be missing?
prefect kubernetes manifest orion
Anna Geller07/01/2022, 1:05 AM
Zanie07/01/2022, 1:07 AM
locally and the
in the container. These values should match.
tells the UI where to have clients (e.g. your web browser) make API requests to.
Anna Geller07/01/2022, 1:24 AM
Zanie07/01/2022, 1:28 AM
Michał Augoff07/01/2022, 2:44 AM
. I then set
inside my local
(default profile) to
and this seems to be enough to query the API to create/get work queues, log flow runs, create deployments etc. When I open the same exact URL in my browser, I see prefect UI but there’s no data in there. Are you saying I also need to set
PREFECT_API_URL = "http://<POD-IP>:4200/api"
container? Isn’t it set to
by default? (and
by default is set to local inside the API container). To clarify, I do not interact with my local
at all (in fact I deleted it from
, so it doesn’t even exist), just the db running inside the pod
locally does help in the sense that I’m able to interact with the k8s api at
prefect orion start
but obviously I’d like to do it directly at
without running a server locally
Zanie07/01/2022, 3:53 AM
Are you saying I also need to setYes, to the URL that users of the UI need to make API requests. This is because the requests to the API come from the user’s browser, not local to the UI pod.inside the
Michał Augoff07/01/2022, 4:44 AM