unkin/argocd-apps
2
0
Fork 0
Code Issues 2 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

feat(open-webui): deploy Open WebUI using litellm for model interaction #155

New Issue
Open
opened 2026-05-24 12:03:26 +10:00 by unkinben · 0 comments
unkinben commented 2026-05-24 12:03:26 +10:00
Owner
Copy Link
Copy Source

Overview

Deploy Open WebUI — a self-hosted web interface for interacting with AI models.

Requirements

  • Namespace: open-webui (or aitooling)
  • ArgoCD project: aitooling
  • Gateway: traefik-external gatewayclass (internet-accessible)
  • Model backend: Route through the existing litellm deployment (already deployed in litellm namespace)
  • Storage: PostgreSQL (CNPG) for persistent chat history/settings, or SQLite (investigate)

Research needed

  • Confirm Docker image: ghcr.io/open-webui/open-webui — check latest tag and available variants
  • Review Open WebUI docs for LiteLLM/OpenAI-compatible backend configuration
  • Determine storage requirements: SQLite (ephemeral PVC) vs PostgreSQL (CNPG)
  • Check if machine-learning/embedding features need a separate sidecar
  • Autoscaling: is Open WebUI stateless enough for HPA, or does session state require sticky sessions?
  • Auth: review OAuth/SSO options (integrate with Kanidm?)
  • Confirm connection details to litellm: http://litellm-pooler.litellm.svc.cluster.local:4000

Implementation notes

  • Add Open WebUI image to apps/base/artifactapi/resources/conf.d/remote-docker.yaml in a separate PR
  • Configure OPENAI_API_BASE_URL to point to litellm ClusterIP service
  • Use VaultStaticSecret for any API keys or credentials
  • External hostname: chat.k8s.syd1.au.unkin.net or similar (TBD)

References

## Overview Deploy [Open WebUI](https://github.com/open-webui/open-webui) — a self-hosted web interface for interacting with AI models. ## Requirements - **Namespace**: `open-webui` (or `aitooling`) - **ArgoCD project**: aitooling - **Gateway**: `traefik-external` gatewayclass (internet-accessible) - **Model backend**: Route through the existing `litellm` deployment (already deployed in `litellm` namespace) - **Storage**: PostgreSQL (CNPG) for persistent chat history/settings, or SQLite (investigate) ## Research needed - [ ] Confirm Docker image: `ghcr.io/open-webui/open-webui` — check latest tag and available variants - [ ] Review Open WebUI docs for LiteLLM/OpenAI-compatible backend configuration - [ ] Determine storage requirements: SQLite (ephemeral PVC) vs PostgreSQL (CNPG) - [ ] Check if machine-learning/embedding features need a separate sidecar - [ ] Autoscaling: is Open WebUI stateless enough for HPA, or does session state require sticky sessions? - [ ] Auth: review OAuth/SSO options (integrate with Kanidm?) - [ ] Confirm connection details to litellm: `http://litellm-pooler.litellm.svc.cluster.local:4000` ## Implementation notes - Add Open WebUI image to `apps/base/artifactapi/resources/conf.d/remote-docker.yaml` in a **separate PR** - Configure `OPENAI_API_BASE_URL` to point to litellm ClusterIP service - Use VaultStaticSecret for any API keys or credentials - External hostname: `chat.k8s.syd1.au.unkin.net` or similar (TBD) ## References - GitHub: https://github.com/open-webui/open-webui - Docs: https://docs.openwebui.com/
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#155
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?