Question

You are managing a Deployment named 'payments' with 3 replicas. The team wants each replica to run on a different node for high availability, but they notice all 3 pods have been scheduled onto the same node. Which addition to the pod template will BEST guarantee that the scheduler spreads the replicas across separate nodes?

Accepted Answer

A podAntiAffinity rule under requiredDuringSchedulingIgnoredDuringExecution matching the pod's own label with topologyKey 'kubernetes.io/hostname'

Answer

A nodeSelector matching the label 'kubernetes.io/hostname' on each pod

Answer

A podAffinity rule under requiredDuringSchedulingIgnoredDuringExecution matching the pod's own label with topologyKey 'kubernetes.io/hostname'

Answer

A NoSchedule taint on each node so only one pod lands per node