Split Zoekt updateStrategy value for both gateway deployment and zoekt statefulset

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

What does this MR do and why?

This MR splits the updateStrategy value so that can be used separately for the Gateway Deployment and the Zoekt StatefulSet. Using the same value for both is risky, since updateStrategy children for Deployments and Statefulset may have difference elements according to the Kubernetes API.

• RollingUpdateStatefulSetStrategy: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.28/#rollingupdatestatefulsetstrategy-v1-apps
  • Contains maxUnavailable and partition fields.
• DeploymentStrategy: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.28/#deploymentstrategy-v1-apps
  • Contains maxSurge and maxUnavailable fields.

In addition to this, please note that using updateStrategy.maxUnavailable in Statefulsets is only available for K8s clusters with version >=1.24. For some reason, in GitLab version 17.7 this is detected as an error at the time of deploying, introducing a breaking change.

See https://support.gitlab.com/hc/requests/601353 for further information.