Comment 2 for bug 1834060

As a workaround, we are implementing a flavor-based placement strategy where we'll target workers per compute node via flavor extra_specs=capabilities:host:<hypervisor_hostname> and then setting the machine constraints for the placement to use those hypervisor-tagged flavors, along with ensuring ComputeCapabilitiesFilter is part of the nova placement filters.

This seems a sufficient strategy for kubernetes-worker nodes, and then using AZ placement flavors for k8s-master, etcd, kubeapi-load-balancer, etc.