Feature: Support spreading nodes across multiple VC

[sidharthsurana]

When deploying a machineset, we should support specifying a different VC in the spec that overrides the VC specified in the cluster object. This way from the infrastructure point of view, we can spread the node VMs across VCs. In doing so that assumption is that the user deploying this cluster will make sure that the VMs created across the VC will have a proper L3 connectivity to each other.

[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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[moshloop]

What is the benefit of this? Deploying across multiple vSphere clusters I fully agree with, but that can be done with a single vCenter?

within a single VC #175 would cover that use case.

[akutz]

Hi @moshloop,

I think I agree with you. Let's allow the affinity rules cover how these are spread out. While long-term there may be benefits (cross-site redundancy) of machines across multiple vCenters, I'm not sure short-term it's necessary to prioritize this.

I'd rather push back on vSphere product group to enhance affinity rules to support cross-vCenter migration.

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

[dimatha]

What is the benefit of this? Deploying across multiple vSphere clusters I fully agree with, but that can be done with a single vCenter?

within a single VC #175 would cover that use case.

We do have a use case for that. Examples:

• On-prem vCenter and VMC, different vxrail clusters deployed with its own venter (for various reasons)
• Migration of the clusters from one vcenter to another