[WIP] 🌱 Clusterctl move Cluster Principal

[fabriziopandini]

What this PR does / why we need it:
This PR extends clusterctl move so it will manage to move the cluster principal objects introduced for addressing CAPA multitenancy (kubernetes-sigs/cluster-api-provider-aws#1753).
NB. the implementation is generic, so it will work for any infrastructure provider implementing a similar solution.

NB.
this PR will remain WIP until kubernetes-sigs/cluster-api-provider-aws#1753 merges

Which issue(s) this PR fixes:
Fixes #3081

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign fabriziopandini
You can assign the PR to them by writing /assign @fabriziopandini in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• cmd/clusterctl/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fabriziopandini]

/assing @randomvariable
/assing @vincepri

[vincepri]

/milestone v0.3.x

Going to hold this until after v0.3.7 is cut

[fabriziopandini]

/test pull-cluster-api-test

[CecileRobertMichon]

NB. the implementation is generic, so it will work for any infrastructure provider implementing a similar solution.

Can we document this in https://cluster-api.sigs.k8s.io/clusterctl/provider-contract.html ?

[fabriziopandini]

Can we document this in https://cluster-api.sigs.k8s.io/clusterctl/provider-contract.html

Sure. I have a PR ready with the documentation for the three clusterctl PRs I have in flight

[k8s-ci-robot]

@fabriziopandini: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fabriziopandini]

@randomvariable is there any ETA about the proposal for Cluster Principal in CAPA, so I can properly prioritize this work?

[randomvariable]

@fabriziopandini Proposal is in, implementation is in some part of the 0.5.x series, not the 0.5.5 that is currently in the process of being released.

[vincepri]

/milestone v0.4.0

[vincepri]

@fabriziopandini Can this be closed?

[fabriziopandini]

/close
We can reopen once the changes lands on CAPA
@randomvariable ^^

[k8s-ci-robot]

@fabriziopandini: Closed this PR.

In response to this:

/close
We can reopen once the changes lands on CAPA
@randomvariable ^^

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.