What does "topology spread constraints" allow you to configure for Pod scheduling, and how does it differ from anti-affinity?
Correct! Well done.
Incorrect.
The correct answer is B) Topology spread constraints let you specify how Pods spread across domains (e.g. zones, nodes) using "maxSkew" to control allowed imbalance, giving finer, more scalable control than anti-affinity rules, which grow complex at scale
Correct Answer
Topology spread constraints let you specify how Pods spread across domains (e.g. zones, nodes) using "maxSkew" to control allowed imbalance, giving finer, more scalable control than anti-affinity rules, which grow complex at scale
While anti-affinity rules can approximate spreading by avoiding co-location, topology spread constraints provide a more direct and scalable mechanism (via maxSkew and topology keys) to balance Pods evenly across zones, nodes, or other domains.