Add deployment strategy configuration to Trino gateway

Author: sdaberdaku

charts/gateway/README.md

@@ -165,6 +165,9 @@ A Helm chart for Trino Gateway
 * `serviceAccount.name` - string, default: `""`  
 
   The name of the service account to use. If not set and create is true, a name is generated using the fullname template
+* `strategy` - object, default: `{"rollingUpdate":{"maxSurge":"25%","maxUnavailable":"25%"},"type":"RollingUpdate"}`  
+
+  The deployment strategy to use to replace existing pods with new ones.
 
 ----------------------------------------------
 Autogenerated from chart metadata using [helm-docs v1.14.2](https://github.com/norwoodj/helm-docs/releases/v1.14.2)

charts/gateway/templates/deployment.yaml

@@ -20,6 +20,8 @@ spec:
   {{- if not .Values.autoscaling.enabled }}
   replicas: {{ .Values.replicaCount }}
   {{- end }}
+  strategy:
+    {{- toYaml .Values.strategy | nindent 4 }}
   selector:
     matchLabels:
       {{- include "trino-gateway.selectorLabels" . | nindent 6 }}

charts/gateway/values.yaml

@@ -213,3 +213,10 @@ serviceAccount:
   # -- The name of the service account to use.
   # If not set and create is true, a name is generated using the fullname template
   name: ""
+
+# -- The deployment strategy to use to replace existing pods with new ones.
+strategy:
+  type: RollingUpdate
+  rollingUpdate:
+    maxSurge: 25%
+    maxUnavailable: 25%