Multi-tenant support with a single manager instance

[gab-satchi]

/kind feature

Describe the solution you'd like
CAPV manager currently requires credentials to a vcenter through its runtime options to operate. This issue is to track support for multi-tenancy through a single instance of the CAPV manager.

There are currently less than ideal ways to deploy to multiple vcenters:

• Utilize the Server field in vsphere machine clone spec. This allows for machines to be deployed to vcenters other than the one the manager is configured for, but it requires the alternate vcenters to have the same credentials as the primary one.
• Deploy multiple instances of the CAPV manager configured for each vcenter and have them watch a dedicated namespace. Not currently supported and may never be fully supported. CAPI's multi-tenancy contract implicitly calls for a single manager instance.

Anything else you would like to add:
Each cluster will need to specify credentials to be used to deploy the cluster, if it's something other than what the CAPV manager is configured for. This could be done through a reference to a secret. If a cluster doesn't specify credentials, CAPV can fall back to using the credentials configured in the manager.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[gab-satchi]

/remove-lifecycle stale