🐛 ClusterClass: patch MachineDeployment selector authoritatively #5731
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.
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
The labels we apply to the MD changed slightly from v1.0 to main (in the cluster topology reconciler). As we were only patching the metadata.labels but not the selector authoritatively the topology reconciler wasn't able to patch the labels (because the webhook enforces that the metadata.labels match the selector)
Slightly more context: https://kubernetes.slack.com/archives/C8TSNPY4T/p1637763270197700?thread_ts=1637762697.197400&cid=C8TSNPY4T
Verified locally in addition to the unit test by:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #