Discrepancies in TopologySpreadConstraints in operator & helmChart

[Kavinraja-G]

Looks like operator accepts the topologySpreadConstraint for statefulset as object whereas helmChart accepts as array for the same field.

From operator --

➜ kubectl explain redpanda.spec.clusterSpec.statefulset.topologySpreadConstraints
GROUP:      cluster.redpanda.com
KIND:       Redpanda
VERSION:    v1alpha1

FIELD: topologySpreadConstraints <Object>

DESCRIPTION:
    Defines topology spread constraints to control how Pods are spread across
    different topology domains.

FIELDS:
  maxSkew	<integer> -required-
    Defines the maximum skew between the number of Pods in any two topology
    domains.

  topologyKey	<string> -required-
    Specifies the topology key to use for spreading Pods.

  whenUnsatisfiable	<string> -required-
    Sets the policy for how to handle unsatisfiable constraints, such as
    `DoNotSchedule` or `ScheduleAnyway`.

From helm --
https://github.com/redpanda-data/helm-charts/blob/main/charts/redpanda/values.yaml#L711-L714

  topologySpreadConstraints:
  - maxSkew: 1
    topologyKey: topology.kubernetes.io/zone
    whenUnsatisfiable: ScheduleAnyway

JIRA Link: K8S-213