-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add guide on how to expose KubeAI Server and OpenWebUI via Ingress #252
Comments
For info I used the following values.yaml to enable ingress. By default this tries to expose kubeai server, when you probably want Open WebUI or both. ...
ingress:
enabled: true
className: traefik-internal
annotations:
cert-manager.io/cluster-issuer: my-vault-issuer
cert-manager.io/common-name: kubeai.internal.mydomain.net
traefik.ingress.kubernetes.io/router.middlewares: traefik-middleware-redirect-to-https@kubernetescrd
rules:
- host: kubeai.internal.mydomain.net
paths:
- path: /
pathType: Prefix
tls:
- secretName: kubeai-tls-secret
hosts:
- kubeai.internal.mydomain.net |
This is how I used with Gateway API to publish L7.
|
I appreciate the shared configurations for enabling Ingress and using the Gateway API to expose KubeAI Server. I was wondering if there are any official or community tutorials that provide a guide on how to expose these services to the public using Ingress and a Load Balancer (LB) on AWS EKS(https://www.kubeai.org/installation/eks/) @samos123 |
@nstogner @samos123 your open-webui subchart is defined to be a very old version. |
@sjoerdvandenbos-prodrive we've switched to upstream helm chart of Open WebUI: #379 We plan to do a new release soon of the KubeAI helm chart that will use the upstream helm chart with a newer version. |
No description provided.
The text was updated successfully, but these errors were encountered: