Support readinessProbe/livenessProbe/startupProbe in the pipelines chart
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Start with values.yaml and templates/deployment.yaml in the pipelines chart at the open-webui-16.5.0 layout described in the issue. Check how the container spec is rendered, then add optional readinessProbe, livenessProbe, and startupProbe values with empty defaults. Done means the chart renders each configured probe and remains unchanged when the values are omitted.
Written by the indexing model from the issue text.
Description
We are using the pipelines chart and noticed there is no way to set readinessProbe, livenessProbe or startupProbe. We checked values.yaml and templates/deployment.yaml in the newest version (open-webui-16.5.0) and this option is not there.
This is a problem for us because our pipelines need some time to start (they import custom pipeline files, and some of them also install dependencies). Without a readiness probe, Kubernetes thinks the pod is ready right after the container process starts, not after the app really finished loading. So during a rolling update, the old pod can get removed before the new one is actually able to answer requests, and this can cause some requests to fail even though the deployment shows as successful.
I could offer the PR with optional readinessProbe, livenessProbe and startupProbe values (default {}, so nothing changes for people who don't use it), and template them into the container spec, something like:
{{- with .Values.readinessProbe }}
readinessProbe:
{{- toYaml . | nindent 12 }}
{{- end }}
This way each user can point the probe to whatever health endpoint makes sense for their own pipelines, the chart does not need to know anything about that.
If this is something you would accept, I can create a PR for those changes. Should be a small change and should not affect anyone who is not using it.
- Dominant language
- Go Template
- Stars
- 290
- Forks
- 158
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-webui/helm-charts
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-webui/helm-charts#425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/helm-charts#423 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 82/100
open-webui/helm-charts#442 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
open-webui/helm-charts#431 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
open-webui/helm-charts#427 · 1 comment ·
All issues in open-webui/helm-charts
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openedx/openedx-authz#460 ·