Kubernetes pod anti-affinity vs topology spread for stateful workloads

Running a stateful set across 3 AZs and trying to balance between strict anti-affinity (which causes scheduling failures during node replacements) and topology spread constraints (which are softer but risk uneven distribution). What is the right approach when you need both resilience and high availability during cluster maintenance?