Parametrize rollingUpdate parameters for Moon deployment

aerokube · May 6, 2023 · ac83713 · ac83713
1 parent 61fb464
commit ac83713
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/moon2/templates/deployment.yaml b/moon2/templates/deployment.yaml
@@ -18,6 +18,11 @@ spec:
   selector:
     matchLabels:
       app: {{ .Release.Name }}
+  strategy:
+    rollingUpdate:
+      maxSurge: {{ .Values.deployment.rollingUpdate.maxSurge | default 1 }}
+      maxUnavailable: {{ .Values.deployment.rollingUpdate.maxUnavailable | default 1 }}
+    type: RollingUpdate
   template:
     metadata:
       annotations:

diff --git a/moon2/values.yaml b/moon2/values.yaml
@@ -286,6 +286,14 @@ deployment:
   securityContext: {}
   #  runAsUser: 1000
 
+  ##
+  ## Optional fields that specifies the maximum number of pods that can be created over the desired number of pods
+  ## and that can be unavailable during the update. You can use both int and percent values.
+  ##
+  rollingUpdate: {}
+  #    maxSurge: 25%
+  #    maxUnavailable: 25%
+
   ##
   ## Node Selector for Moon pods
   ##