fix: set maxUnavailable to 1 when its 0 to avoid an infinite loop#1932
Merged
fix: set maxUnavailable to 1 when its 0 to avoid an infinite loop#1932
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
AndrewChubatiuk
approved these changes
Mar 5, 2026
AndrewChubatiuk
pushed a commit
that referenced
this pull request
Mar 19, 2026
AndrewChubatiuk
pushed a commit
that referenced
this pull request
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We're breaking a list of pods to restart into batches, based on
o.maxUnavailablevalue. However, it can be misconfigured and resolve into 0 (e.g.50%on one pod). This would result into infinite loop.This clamps the value to 1 and adds tests for similar situation