Fix interactive rolling update silently ignored #5642
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.
This improves on #4166 (Interactive cli opt) by adding
--interactive
support for rolling updates in--cloudonly
mode and for feature flagDrainAndValidateRollingUpdate
disabled. Without this fix, the interactive flag is silently ignored.Why is this change needed: it's not currently obvious the interactive mode does not always work. Also, I'd say interactive rolling update is most useful when the validation is turned off or the upgrade is cloud only.
Originally there were four (!) cases with only the penultimate one using the interactive prompt:
This PR only adds the prompt after removing any cluster node. Bastion nodes still do not prompt.
As for the implementation:
continue
after bastion upgrade to not trigger the prompt.DeleteInstance
methodTests: there were no tests in the original pr #4166 and I'm not quite sure how to test this on CI. I've run the upgrade locally though and the command works as expected.
/area rolling-update