Hi everyone!I am having an issue with deploying Prefect UI, and would like to know how to get around it.When I use Helm to deploy prefect on Kubernetes, I cannot set an ingress path as fully qualified URL with a segment. i.e. Something like
Hi @Ahsan Tanweer, I’d love to help but this seems to be a very infrastructure-specific DevOps issue that would require looking at your networking setup. I could put you in touch with a team who specializes in infrastructure issues like this and provides more in-depth guidance.
9 months ago
Hi Anna!Thank you for replying.To be fair, it’s a normal kubernetes cluster, and I did a regular helm install by following the docs. I think I over did my explanation 😄This issue (from my understanding) can be fixed, if
environment var is used when fetching static files (which I believe is how it was intended, but an oversight was made?).That said, I would love if you can get me in touch with someone who specialises in infrastructure, and if they can guide me if I am approaching this wrong.
So after reviewing your request:1. We don’t support what you are describing. I recommend using subdomains if you want a more clear URL for your resources.
2. You can build your own version of the UI with a different base URL, the UI is open source and code can be found at
9 months ago
Right now I have done exactly this. Set up UI on another subdomain (outside K8s), configured it for the CORS. It is just that we have operational limitations of subdomains within a Kubernetes cluster.
And yes rebuilding the ui container with differing configuration should fix it. It just takes the convenience of everything auto-magically working with official Helm. 😄I wanted to gauge the plans/limitations for prefect as we use it for our needs.
I think I will tinker a bit with the docker images and helm charts to make them fit for my purpose.
Thank you for your prompt replies and checking this through! 🙂