✨ Pass the new GVK flag to azure manager #646
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.
What this PR does / why we need it:
Since the introduction of the flags upstream in
And implementing upstream kubernetes-sigs/cluster-api-provider-azure#4854, we need some changes to our turtles provider.
The CAPZ supports using different
GVK
for establishing controller to watch over changes within the bootstrap token. With that turtles will be able to leverage this flag for any user creatingazure
CAPIProvider
.The default value (set to watch
RKE2Config
for us) of the CLI flag can be overridden, if theCAPIProvider
resource has additionally specified:This allows to run the CAPZ with
kubeadm
bootstrap/controlPlane provider if required.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 #633
Special notes for your reviewer:
Checklist: