https://prefect.io
Join Slack
Hey, folks, on my continuing quest to install prefect-server in k8s, I've got the helm install (most...
# prefect-kubernetes
a
Hey, folks, on my continuing quest to install prefect-server in k8s, I've got the helm install (mostly) working, but the UI is reacting...weirdly. When I go to the exposed URL of the server, the settings page looks like this:
This is running container version 
2.10-python3.11-kubernetes
installed via a slightly-modified helm chart to get MetalLB exposure working
I'm also seeing a ton of 405-errors from the browser to the web ui
I presume there's some assumption about running the server component in k8s, but I'm not sure what it is at the moment.
just tried with version 
2.8.7-python3.11
and getting the same results.
j
Did you try using port-forward to the service? That would rule out issues related to your ingress or load balancer
a
I did. Doing it the naive way had the same result because the 
PUBLIC_API_URL
was still pointed at the loadbalancer address. I re-installed it with the apiUrl and the apiHost set to 
127.0.0.1
, tried the port-forward, and got the same thing.
My suspicion is that if the load balancer weren't working I wouldn't get any response, rather than an empty html file.
(especially since I'm doing this with MetalLB rather than ingress, so it's not trying to interpret the http)
Ugh. Apologies. I figured it out. For the record: 
publicApiUrl
needs to end in 
/api
...my helm chart did not have that set properly, it just had the base url 
<http://prefect-server:4200>
. Hence the weirdness.
Open in Slack
PreviousNext
Powered by

Prefect Community

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.

Powered by