Fixed deployment readiness (operational status) detection after resource update #1152
Conversation
This file contains 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
…e. The algorithm is taken from the `kubectl rollout status` command.
Amper
force-pushed
the
fix-single-ready-status-after-update
branch
from
046948a
to
801bf7b
Compare
Amper
requested review from
f41gh7,
Haleygo and
AndrewChubatiuk
as code owners
|
Thanks for contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The algorithm is taken from the
kubectl rollout statuscommand.Currently (before this update), the operator sets status operational ahead of time - when vmsingle pods are still restarting.