You applied this podAntiAffinity rule but pods are still scheduled on the same node:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchLabels:
app: frontend
topologyKey: invalid-keyWhat is the most probable cause?
AThe rule is preferred, not required, so pods can still schedule on the same node.
BThe <code>labelSelector</code> is incorrect because it should use <code>matchExpressions</code> instead of <code>matchLabels</code>.
CThe <code>topologyKey</code> value <code>invalid-key</code> does not match any valid node label, so the rule is ignored.
DThe podAntiAffinity rule must be defined under <code>podAffinity</code> to work correctly.
