Update Progressing
condition on machineDeployment for nil progressDeadlineSeconds
#762
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.
What this PR does / why we need it:
Currently when
progressDeadlineSeconds
is nil , then noProgressing
condition is added to machineDeployment. This PR adds that condition now.In gardener, currently we deploy machineDeployments with this field as
nil
, but we would also like to see if the deployment is rollingUpdating or not. Now that this condition would be present, we could achieve that.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: