Added support for relative values in scheduling.minAvailable

nano-byte · Sep 20, 2024 · dd7105d · dd7105d
1 parent 9c99703
commit dd7105d
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 2 deletions.
diff --git a/charts/generic-service/ci/relative-min-available-values.yaml b/charts/generic-service/ci/relative-min-available-values.yaml
@@ -0,0 +1,10 @@
+# Relative minimum availability test
+
+image:
+  repository: jwilder/whoami
+  tag: latest
+
+replicas: 3
+
+scheduling:
+  minAvailable: 50%
diff --git a/charts/generic-service/templates/pdb.yaml b/charts/generic-service/templates/pdb.yaml
@@ -1,4 +1,4 @@
-{{- if and (gt .Values.scheduling.minAvailable 0.0) (lt .Values.scheduling.minAvailable .Values.replicas) }}
+{{- if or (kindIs "string" .Values.scheduling.minAvailable) (and (gt .Values.scheduling.minAvailable 0.0) (lt .Values.scheduling.minAvailable .Values.replicas)) }}
 
 apiVersion: policy/v1
 kind: PodDisruptionBudget

diff --git a/charts/generic-service/values.schema.json b/charts/generic-service/values.schema.json
@@ -587,7 +587,7 @@
           "description": "How to spread replicas across nodes"
         },
         "minAvailable": {
-          "type": "integer",
+          "type": ["integer", "string"],
           "default": 1,
           "description": "Minimum number of instances to keep running during cluster maintenance (only applied if this value is smaller than replicas)"
         }