Mixed infra provider support

[vxav]

We have been experimenting with mixed infra providers implementations. Namely running the control plane nodes in vSphere with a node pool in e.g. Proxmox (what we have handy).

This technically works but I needed to add some logic to the CCM to exclude nodes with .spec.ProviderID != vsphere:// || null, otherwise the vSphere CCM would boot the proxmox nodes out of the cluster because it can't find the VM in vCenter.

Note that this internal PR is draft and testing only but I wanted to know if there would be some interest in supporting this upstream?

giantswarm#1

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten