`maxUnavailable: 0` can cause problems when `replica: 1`
Open
Nobody has claimed this yet.
bug
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Because the deployment (if unhealthy) never gets into a very happy state / cannot roll over
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 locating the Helm deployment configuration that handles maxUnavailable and replica, then reproduce the unhealthy rollout with replica set to 1 and maxUnavailable set to 0. Done means the chart no longer permits the reported rollout problem or clearly documents the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100