The maxUnavailablePods field in values.yaml does not work

[yandongxiao]

Describe the bug

We have added the following flag to api server

- --feature-gates=MaxUnavailableStatefulSet=true

When we added the field in values.yaml

  # Max unavailable pods for the cn component when doing rolling update.
  # This field cannot be 0. The default setting is 1.
  # Note: Because Operator uses statefulset to manage this component, the maxUnavailable field is in Alpha stage, and it is honored
  # only by API servers that are running with the MaxUnavailableStatefulSet feature gate enabled.
  # See https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#maximum-unavailable-pods for more details.
  maxUnavailablePods:

After upgarding helm chart, the statefulset spec doesn't contain .spec.updateStrategy.rollingUpdate.maxUnavailable field

  updateStrategy:
    type: RollingUpdate
    rollingUpdate:
      partition: 0

Expected behavior

the statefulset spec should have update in updateStrategy fields.

Please complete the following information

• Operator Version: v1.9.10
• Chart Name: kube-starrocks
• Chart Version v1.9.10