Feature: enhanced maxSurge performance #1929
Draft
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.
Ⅰ. Describe what this PR does
CloneSet can retain both old and new version Pods simultaneously in some upgrade scenarios (such as blue-green release) by setting
minReadySeconds
to a sufficiently large value along with a suitablemaxSurge
. However, during the above upgrade process, it's not possible to dynamically adjust the number of new Pods by changingmaxSurge
in real-time. This update adds such capability to CloneSet.Ⅱ. Does this pull request fix one issue?
fixes #1666
Ⅲ. Describe how to verify it
change maxSurge while updating
Ⅳ. Special notes for reviews