From ac83713ab04022199b63f907e2faea247f0c74d8 Mon Sep 17 00:00:00 2001
From: sergey <sergey@aerokube.com>
Date: Sat, 6 May 2023 19:22:13 +0200
Subject: [PATCH] Parametrize rollingUpdate parameters for Moon deployment

---
 moon2/templates/deployment.yaml | 5 +++++
 moon2/values.yaml               | 8 ++++++++
 2 files changed, 13 insertions(+)

diff --git a/moon2/templates/deployment.yaml b/moon2/templates/deployment.yaml
index a8ca0c2..508b008 100644
--- 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
index fe080ec..0576497 100644
--- 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
   ##