How crisp-sh/helm-charts works
Project type and purpose
• This is a chart repository (Helm charts) for packaging and deploying two logical applications into a Kubernetes cluster:
a. open-webui (the core web UI + supporting services)
b. pipelines (a pipeline orchestration component)
• The README confirms the purpose: hosting and distributing Helm charts for Open WebUI.
File structure
• Top-level: .github/workflows (CI/CD), charts/, package.json, config files.
• Under charts/ you have two subdirectories:
• open-webui/
• pipelines/
• Each chart contains standard Helm artifacts: Chart.yaml, values.yaml (+ env-specific overrides), and Kubernetes templates (deployment.yaml, service.yaml, ingress.yaml, PVC, ServiceAccount, extra resources, etc.).
README for additional insights
• Implied use cases: users will install these charts into their own Kubernetes clusters (GKE, Minikube), deploying a web UI and pipeline automation side by side or separately.
Main components and their relationships
a. Helm Chart Repository
• Contains two charts; published to https://helm.openwebui.com.
• CI/CD workflows automatically lint, test, and release charts via GitHub Actions.
b. Kubernetes Cluster
• Two namespaces (or one shared) each for open-webui and pipelines.
• Deployments & Services for pods.
• Ingress configured for the web UI (with managed certificate).
• Redis (via a websocket-redis.yaml) for real-time messaging.
• PVC for persistent storage.
c. External Users & Clients
• End users access the Web UI via Ingress/load balancer endpoint.
• Pipeline clients may interact via API/service endpoints.
d. CI/CD Pipeline (GitHub Actions)
• Lint and test charts (helm-test-*.yml).
• Automate releases (helm-release.yml).
Architectural patterns and design principles
• Declarative Infrastructure: All Kubernetes resources are defined as code in Helm templates.
• Environment-specific overrides: values-gke-min.yaml, values-minikube.yaml.
• Separation of Concerns:
• Web UI layer (Ingress → Service → Deployment pods + Redis)
• Pipeline layer (ServiceAccount → Deployment → Service)
• CI/CD as Code: GitHub workflows orchestrate chart testing and publishing.
Technologies, frameworks, libraries
• Helm (charts, templating engine)
• Kubernetes API objects (Ingress, Deployment, Service, PVC, ServiceAccount, ConfigMaps)
• GitHub Actions (CI/CD)
• External DNS/Managed Cert (GKE Ingress add-on or cert-manager)
• Redis (messaging backend for WebSocket)