We built a guided install mission for Open WebUI inside KubeStellar Console, a standalone Kubernetes dashboard (unrelated to legacy kubestellar/kubestellar, kubeflex, or OCM — zero shared code).
The mission installs Open WebUI via the official Helm chart at https://helm.openwebui.com/ , wires it to an in-cluster OpenAI-compatible backend (Ollama / vLLM / LocalAI / llama.cpp / RHAIIS) via the OPENAI_API_BASE_URL env var, and exposes it through a ClusterIP Service. Each step:
Pre-flight — confirms one of the supported backend runners is already installed and reachable
Commands — helm repo add open-webui https://helm.openwebui.com/, then helm install open-webui with an inline values file pointing at the backend Service
Validation — rollout status, PVC binding, and a curl to the web UI's port-forwarded endpoint to confirm sign-up and model picker work
Open WebUI is also registered as a chat-capable provider in the Console's own agent selector via the OPEN_WEBUI_URL env var, so Console chat can route through Open WebUI for users who prefer that UI.
Why we're reaching out
The Console now ships with local-LLM runner integrations. Open WebUI plays the "frontend" role — it is the only runner in the set that proxies to another backend rather than doing inference itself. That makes it the right first-stop UI for many operators, and we wanted you to know we integrated against it.
Install
Local (connects to your current kubeconfig context):
Mission definitions are open source — PRs welcome at install-open-webui.json. Feel free to close if not relevant.
Originally created by @clubanderson on GitHub (Apr 16, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23769
We built a guided install mission for Open WebUI inside [KubeStellar Console](https://console.kubestellar.io?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=open-webui), a standalone Kubernetes dashboard (unrelated to legacy kubestellar/kubestellar, kubeflex, or OCM — zero shared code).
→ **[Open the Open WebUI install mission](https://console.kubestellar.io/missions/install-open-webui?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=open-webui)**
### What the mission does
The mission installs Open WebUI via the official Helm chart at https://helm.openwebui.com/ , wires it to an in-cluster OpenAI-compatible backend (Ollama / vLLM / LocalAI / llama.cpp / RHAIIS) via the `OPENAI_API_BASE_URL` env var, and exposes it through a ClusterIP Service. Each step:
1. **Pre-flight** — confirms one of the supported backend runners is already installed and reachable
2. **Commands** — `helm repo add open-webui https://helm.openwebui.com/`, then `helm install open-webui` with an inline values file pointing at the backend Service
3. **Validation** — rollout status, PVC binding, and a `curl` to the web UI's port-forwarded endpoint to confirm sign-up and model picker work
4. **Troubleshooting** — empty model picker (backend unreachable, NetworkPolicy blocking egress), sign-up failures (`ENABLE_SIGNUP` not set), PVC stuck Pending, RAG upload OOMs
5. **Rollback** — `helm uninstall` + PVC + namespace cleanup
Open WebUI is also registered as a chat-capable provider in the Console's own agent selector via the `OPEN_WEBUI_URL` env var, so Console chat can route through Open WebUI for users who prefer that UI.
### Why we're reaching out
The Console now ships with local-LLM runner integrations. Open WebUI plays the \"frontend\" role — it is the only runner in the set that proxies to another backend rather than doing inference itself. That makes it the right first-stop UI for many operators, and we wanted you to know we integrated against it.
### Install
Local (connects to your current kubeconfig context):
```bash
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash
```
Deploy into a cluster:
```bash
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/deploy.sh | bash
```
---
Mission definitions are open source — PRs welcome at [install-open-webui.json](https://github.com/kubestellar/console-kb/blob/master/fixes/cncf-install/install-open-webui.json?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=open-webui). Feel free to close if not relevant.
@pr-validator-bot commented on GitHub (Apr 16, 2026):
⚠️ Missing Issue Title Prefix
@clubanderson, your issue title is missing a prefix (e.g., bug:, feat:, docs:).
Please update your issue title to include one of the following prefixes:
bug: Bug report or error you've encountered
feat: Feature request or enhancement suggestion
docs: Documentation issue or improvement request
question: Question about usage or functionality
help: Request for help or support
Example: bug: Login fails when using special characters in password
<!-- gh-comment-id:4256479874 -->
@pr-validator-bot commented on GitHub (Apr 16, 2026):
# ⚠️ Missing Issue Title Prefix
@clubanderson, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`).
Please update your issue title to include one of the following prefixes:
- **bug**: Bug report or error you've encountered
- **feat**: Feature request or enhancement suggestion
- **docs**: Documentation issue or improvement request
- **question**: Question about usage or functionality
- **help**: Request for help or support
Example: `bug: Login fails when using special characters in password`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @clubanderson on GitHub (Apr 16, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23769
We built a guided install mission for Open WebUI inside KubeStellar Console, a standalone Kubernetes dashboard (unrelated to legacy kubestellar/kubestellar, kubeflex, or OCM — zero shared code).
→ Open the Open WebUI install mission
What the mission does
The mission installs Open WebUI via the official Helm chart at https://helm.openwebui.com/ , wires it to an in-cluster OpenAI-compatible backend (Ollama / vLLM / LocalAI / llama.cpp / RHAIIS) via the
OPENAI_API_BASE_URLenv var, and exposes it through a ClusterIP Service. Each step:helm repo add open-webui https://helm.openwebui.com/, thenhelm install open-webuiwith an inline values file pointing at the backend Servicecurlto the web UI's port-forwarded endpoint to confirm sign-up and model picker workENABLE_SIGNUPnot set), PVC stuck Pending, RAG upload OOMshelm uninstall+ PVC + namespace cleanupOpen WebUI is also registered as a chat-capable provider in the Console's own agent selector via the
OPEN_WEBUI_URLenv var, so Console chat can route through Open WebUI for users who prefer that UI.Why we're reaching out
The Console now ships with local-LLM runner integrations. Open WebUI plays the "frontend" role — it is the only runner in the set that proxies to another backend rather than doing inference itself. That makes it the right first-stop UI for many operators, and we wanted you to know we integrated against it.
Install
Local (connects to your current kubeconfig context):
Deploy into a cluster:
Mission definitions are open source — PRs welcome at install-open-webui.json. Feel free to close if not relevant.
@pr-validator-bot commented on GitHub (Apr 16, 2026):
⚠️ Missing Issue Title Prefix
@clubanderson, your issue title is missing a prefix (e.g.,
bug:,feat:,docs:).Please update your issue title to include one of the following prefixes:
Example:
bug: Login fails when using special characters in password