redpanda-data / redpanda-data/redpanda-operator
It is not possible to initiate a rolling restart on a cluster StatefulSet
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 84
- Forks
- 32
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 104
Description
Since the update strategy for the cluster STS is set to Ondelete, we cannot trigger a rolling restart by running k rollout restart sts rp-mycluster.
Can we introduce a way to let the operator know we want to perform a rolling restart of a cluster?
The alternative here is to do it manually by deleting one pod at a time, while waiting for the cluster to become healthy between pod deletions.
JIRA Link: K8S-216
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.
Research direction
No files or tests are named. Start by tracing the operator's cluster StatefulSet reconciliation and how it handles the Ondelete update strategy; determine how a requested rolling restart could be represented and acted on. Done means a cluster operator can request a rolling restart without manually deleting pods, while the cluster remains healthy between pod replacements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100