Worker upgrade started after Pods became Ready #546
Merged
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.
During cluster upgrade, change to start worker node upgrade after all kube-system pods are up and running, instead of immediately updating the control plane after the control plane upgrade is finishe>
The reason for the change is to eliminate service downtime. Prior to this change, some services would be down for tens of seconds during worker node upgrades.
For more information, see the following Issue
Fixes: #537