quickwit-oss / quickwit-oss/helm-charts
Add comments for parallel StatefulSet update
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 37
- Forks
- 43
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 2
Description
Right now, the searcher and indexer StatefulSets are deployed one pod at a time, which can take a long time when users run a large number of pods.
StatefulSets have a feature called .spec.updateStrategy.rollingUpdate.maxUnavailable, which allows pods to be updated in parallel. However, this feature is currently disabled by default. Once it is enabled by default, users should be able to set this field and deploy those pods in parallel.
Note that in order to use this feature, podManagementPolicy needs to be set to Parallel instead of OrderedReady, which is the default. However, since this field is immutable, we cannot change the default policy for existing StatefulSets. The best we can probably do is add comments in values.yaml.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with values.yaml and review the issue's Kubernetes StatefulSet references for updateStrategy. Add comments explaining maxUnavailable, the need for podManagementPolicy: Parallel, and the immutability limitation for existing StatefulSets; done means users can understand how to configure parallel updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100