Open jtv8 opened 6 years ago
We use spec.nodeSelector
labels to accomplish the same ends and the same behaviour occurs. Maybe point 1. could be extended to also include checking of nodeSelector labels for scheduled pods?
edit: I just saw this one: https://github.com/wbuchwalter/Kubernetes-acs-engine-autoscaler/issues/41 my bad, i think my comment relates more to this other one
A common pattern in high availability applications is to set anti-affinity rules so that all the pods of an application run on different nodes: see https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#never-co-located-in-the-same-node
Currently the autoscaler does not know about these rules and so assumes that pods can be scheduled, despite repeatedly appearing as pending in the logs. See example below:
In a future release, it would be helpful to consider one of the two options:
spec.affinity.podAntiAffinity
definition when determining whether pod can be scheduled, or