cluster-api-provider-vsphere
cluster-api-provider-vsphere copied to clipboard
Support for adding created VM to DRS group
/kind feature
Describe the solution you'd like The user is able to specify the name of a vsphere DRS group, and the created vms are added to this DRS group.
This would grant a user better control over VM placement since the DRS group could be used to specify VM-host affinity rules.
Anything else you would like to add: Related - https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/175
Environment:
- Cluster-api-provider-vsphere version:
- Kubernetes version: (use
kubectl version
): - OS (e.g. from
/etc/os-release
):
/assign @akutz
/unassign @akutz /assign
We would be interested in such a feature as well. We run multiple vCenters, some of which in georedundant datacenter setup. So spanning across multiple Clusters within one vCenter would be interesting for us, but also a per-esxi-host approach would allow us to basically make sure that not all masters of a cluster get scheduled on one bladecenter frame for example.
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
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
This has been implemented for some time with VM groups and failure domains.
/close
Feel free to reopen if the current feature set doesn't address your concerns.
@randomvariable: Closing this issue.
In response to this:
This has been implemented for some time with VM groups and failure domains.
/close
Feel free to reopen if the current feature set doesn't address your concerns.
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.