An open-data portal wants Deployment replicas to avoid co-locating on the same host for higher availability. Which scheduling feature helps spread those Pods?
Select an answer to reveal the explanation.
Short Explanation
Anti-affinity is how you tell the scheduler not to stack all your eggs on one node. Service sticky sessions and probe timers do not spread replicas across hosts.
Full Explanation
Pod anti-affinity (preferred or required) influences the scheduler to place Pods relative to other Pods—commonly spreading replicas across Nodes for availability. Service sessionAffinity affects client routing, not replica placement. Probe timings and hostNetwork do not implement anti-affinity spreading.