[rel-v0.12] Fix podManagementPolicy for scale-up scenario #406
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.
How to categorize this PR?
/area high-availability
/kind bug
What this PR does / why we need it:
This PR fixes a bug which caused a scaled-up etcd (
etcd.spec.replicas: 1 -> 3
) cluster having the wrongsts.spec.podManamgentPolicy
.This field must be set to
Parallel
, esp. if the cluster is afterwards scaled down (etcd.spec.replicas: 0
) and scaled up (etcd.spec.replicas: 3
) again. This is a common case when Gardener hibernates and wakes up shoot clusters.Special notes for your reviewer:
/cc @shreyas-s-rao @aaronfern
Release note: