github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #23769] Guided Open WebUI install mission in KubeStellar Console #20064

New Issue
Closed
opened 2026-04-20 02:38:57 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 02:38:57 -05:00
Owner
Copy Link

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_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):

curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash

Deploy into a cluster:

curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/deploy.sh | bash

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.
GiteaMirror commented 2026-04-20 02:38:59 -05:00
Author
Owner
Copy Link

@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`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#20064
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?