Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anti-affinity rule for control plane nodes #539

Open
vxav opened this issue Nov 3, 2023 · 2 comments
Open

Anti-affinity rule for control plane nodes #539

vxav opened this issue Nov 3, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@vxav
Copy link
Contributor

vxav commented Nov 3, 2023

Is your feature request related to a problem? Please describe.

The control plane nodes should be spread on different vSphere hosts.

Describe the solution you'd like

Add an interface to the clusters with flags to:

  • Create affinity rule. Or maybe it's best to create it by default and control the enabled state.
  • Set to should or must (required unchecked)

The members of the anti-affinity rule should be re-evaluated when the cluster is changed (scaling, rolling...).

https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-402BC249-FAD9-408D-90DA-4ADE657B608B.html

Describe alternatives you've considered

No response

Additional context

No response

@dlipovetsky
Copy link
Contributor

What does this require from the VCD provider?

Does it require placement policies?

The CAPVCD types would need to add support for the "failure domain" concept from Cluster API.

@vxav
Copy link
Contributor Author

vxav commented Nov 3, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants