v1alpha4: Clarify and possibly implement changes to multi-tenancy.

[sbueringer]

/kind feature

There have been discussions about changing the way providers handle multi-tenancy. As far as I know the latest version can be found here: https://github.com/kubernetes-sigs/cluster-api/pull/4514/files

I'm trying to clarify if we have to do something before the v0.4.0 release for this: kubernetes-sigs/cluster-api#4514 (comment)

If the PR already applies, we have to drop the possibility to reference secrets for the cloud config from other namespaces: https://github.com/kubernetes-sigs/cluster-api/pull/4514/files#r618619335

P.S. As far as I know this is the last change we (might) need before we can release CAPO v0.4.0.

[sbueringer]

/assign

[sbueringer]

As discussed
/assign @tobiasgiese
/unassign

[k8s-ci-robot]

@sbueringer: GitHub didn't allow me to assign the following users: tobiasgiese.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

As discussed
/assign @tobiasgiese
/unassign

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.

[tobiasgiese]

/assign