Rack Awareness / machinedeployment proxmox host anti-affinity #577
Description
Describe the solution you'd like
I would like to be able to create a nodepool/machinedeployment spread across proxmox hosts such that if a proxmox host fails i don't lose more than N out of M VMs in my pool.
AllowedNodes can specify a subset of proxmox hosts that a VM will be deployed on, but depending on present load it may still deploy multiple VMs onto the same proxmox host. I could define 3 separate machinedeployments each referencing proxmoxmachinetemplate with different list of AllowedNodes, but was curious about whether there was a better way to handle this.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
- Cluster-api-provider-proxmox version: v0.7.4
- Kubernetes version: (use
kubectl version): v1.33.4+rke2r1 - OS (e.g. from
/etc/os-release): management kube cluster - Rocky Linux 9.4 (Blue Onyx), workload cluster - Ubuntu 24.04.3 LTS (Noble Numbat)