add PodDisruptionBudget

charts/mongodb/Chart.yaml

@@ -2,5 +2,5 @@ apiVersion: v2
 name: mongodb
 description: A Helm chart for deploying a mongodb
 type: application
-version: 0.0.14
+version: 0.0.15
 appVersion: 6.0.0

charts/mongodb/templates/poddisruptionbudget.yaml

@@ -0,0 +1,11 @@
+{{- if .Values.maxUnavailable }}
+apiVersion: policy/v1
+kind: PodDisruptionBudget
+metadata:
+  name: "{{ include "common.name" $dot }}-pdb"
+spec:
+  maxUnavailable: {{ .Values.maxUnavailable }}
+  selector:
+    matchLabels:
+      app: {{ include "common.name" $dot }}
+{{- end }}

charts/mongodb/values.yaml

@@ -10,6 +10,10 @@ imagePullSecrets:
 # but if you add 2 for redundancy you will have issues, since voting cannot happen with at least 2 nodes UP
 # meaning if only 2 nodes are there, and one restarts both become secondary and noone gets elected primary
 replicas: 3
+ This is the max unavailable setting for the pod disruption budget
+# The default value of 1 will make sure that kubernetes won't allow more than 1
+# of your pods to be unavailable during maintenance
+maxUnavailable: 1
 addservicename: true
 mongodbPort: 27017
 debugmongodb: false