Support topology spread constraints

[dataviruset]

Describe the solution you'd like Support topology spread constraints for the deployment spec as it's a better way to spread out pods compared to configuring pod anti-affinity.

podAntiAffinity repels Pods. If you set this to requiredDuringSchedulingIgnoredDuringExecution mode then only a single Pod can be scheduled into a single topology domain; if you choose preferredDuringSchedulingIgnoredDuringExecution then you lose the ability to enforce the constraint.

Describe alternatives you've considered Modifying the chart locally or using something like Kustomize to add the field into the deployment spec afterwards, but this feels unnecessarily complicated as I feel topology spread constraint support could benefit many users of this chart.

Additional context Official Kubernetes documentation of the feature