🌱 Add MachinePool test for switching bootstrap config to another ready/non-ready object with different name #9616
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:
If the bootstrap config reference changes, e.g.
KubeadmConfig/{a => b}
, CAPI would previously just return early if the bootstrap secret is ready instead of reconciling towards the new bootstrap config'sdataSecretName
. That was luckily already fixed by #8667. With this PR, I want to add a test that covers the actual use case of switching to a bootstrap config withinMachinePool
.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #8858 (specifically #8858 (comment)), but not a fix.
/area bootstrap