Topology spread constraints look valid but matchLabelKeys exclude the new rollout revision and every new pod lands on one zone

The policy appears healthy on paper, yet only the new ReplicaSet misses the balancing rule because its revision label is not part of the spread match set.