Feature Request | Add support for topologySpreadConstraints

[vijay-wandb]

Similar to how @flamarion added support for the security context in this PR, we need to implement the same for topologySpreadConstraints

Sample block

   topologySpreadConstraints:
        - maxSkew: 1
          topologyKey: kubernetes.io/hostname
          whenUnsatisfiable: ScheduleAnyway
          labelSelector:
            matchLabels:
              control-plane: controller-manager
        - maxSkew: 1
          topologyKey: topology.kubernetes.io/zone
          whenUnsatisfiable: ScheduleAnyway
          labelSelector:
            matchLabels:
              control-plane: controller-manager

[velotioaastha]

Hi @vijay-wandb Can you please confirm if support for topologySpreadConstraints should be added at a global level (meaning it would be same for all the subcharts) or for individual components within their own subchart configurations?

[vijay-wandb]

@velotioaastha Lets go with the global level for now. If it doesn’t work for Ford, I will raise a new FR. Supporting both options in the future could help customers in the long run.

[abhinavg6]

@theishshah will review this

[vijay-wandb]

Hi @theishshah,
Did you have a chance to review this?