Support k8s Gateway API and ingress path prefix #96

New Issue

2026-02-15T19:16:14-05:00

yindo commented

2026-02-15 19:16:14 -05:00

Originally created by @davidshen84 on GitHub (Jul 27, 2025).

Currently, the open-webui chart uses the outdated Ingress resource to define the ingress control and http route.

It should move to the new Kubernetes Gateway API and provide URL prefix rewrite.

Originally created by @davidshen84 on GitHub (Jul 27, 2025). Currently, the open-webui chart uses the outdated [Ingress resource](https://github.com/open-webui/helm-charts/blob/main/charts/open-webui/templates/ingress.yaml#L3) to define the ingress control and http route. It should move to the new [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) and provide URL prefix rewrite.

yindo added the enhancement label 2026-02-15 19:16:14 -05:00

yindo closed this issue

2026-02-15 19:16:15 -05:00

yindo commented

2026-02-15 19:16:15 -05:00

@westbrook-ai commented on GitHub (Aug 7, 2025):

Hey @davidshen84, I started looking at this one and agree with the change, just haven't had the time to implement it yet. PRs are welcome, otherwise this is one of the first issues I'll work on when I get the chance.

@westbrook-ai commented on GitHub (Aug 7, 2025): Hey @davidshen84, I started looking at this one and agree with the change, just haven't had the time to implement it yet. PRs are welcome, otherwise this is one of the first issues I'll work on when I get the chance.

yindo commented

2026-02-15 19:16:15 -05:00

@davidshen84 commented on GitHub (Aug 10, 2025):

The challenge of this is the hardcoded resource URLs, like https://github.com/open-webui/open-webui/blob/main/src/app.html#L5.

There's no easy way to insert the prefix to them.

For backend apps, they are behind the ingress gateway router, and the URL rewrite can handle the prefix easily.

@davidshen84 commented on GitHub (Aug 10, 2025): The challenge of this is the hardcoded resource URLs, like https://github.com/open-webui/open-webui/blob/main/src/app.html#L5. There's no easy way to insert the *prefix* to them. For backend apps, they are behind the ingress gateway router, and the URL rewrite can handle the prefix easily.

yindo commented

2026-02-15 19:16:15 -05:00

@x64nik commented on GitHub (Jan 15, 2026):

I've added Gateway API route template support in PR #339, including automatic HTTP-to-HTTPS redirection via httpsRedirect. I noticed many Gateway API templates don't auto-create HTTP redirect routes, which can be confusing. My implementation automatically creates a separate HTTP route for redirection when enabled, similar to how Ingress handles it.
Would love feedback on this approach!

@x64nik commented on GitHub (Jan 15, 2026): I've added Gateway API route template support in PR #339, including automatic HTTP-to-HTTPS redirection via httpsRedirect. I noticed many Gateway API templates don't auto-create HTTP redirect routes, which can be confusing. My implementation automatically creates a separate HTTP route for redirection when enabled, similar to how Ingress handles it. Would love feedback on this approach!

yindo commented

2026-02-15 19:16:16 -05:00