Provide example on how to bootstrap a self-managed cluster #1008
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:
This is a first attempt at providing a self-managed Rancher cluster.
The goal is to use a throwaway CAPI management cluster to provision a downstream Rancher cluster and pivot to it.
Unfortunately the
move
operation is currently not working.clusterctl does not seem to recognize the providers installed by the cluster-api-operator and fails with:
Note that the move operation succeeds when instead the downstream cluster is also initialized via
clusterctl init
, however this scenario is not suitable for us, as the requirement is to provision a Rancher Turtles ready environment instead.The solution is to implement the
clusteroperator move
command.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 #984
Special notes for your reviewer:
Checklist: