Add support for defining priorityClassName

https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/

Signed-off-by: Giovanni Tirloni <[email protected]>

Author: gtirloni

valkey/README.md

@@ -95,6 +95,7 @@ A Helm chart for Kubernetes
 | podSecurityContext.fsGroup | int | `1000` |  |
 | podSecurityContext.runAsGroup | int | `1000` |  |
 | podSecurityContext.runAsUser | int | `1000` |  |
+| priorityClassName | string | `""` |  |
 | replicaCount | int | `1` |  |
 | resources | object | `{}` |  |
 | securityContext.capabilities.drop[0] | string | `"ALL"` |  |

valkey/templates/deploy_valkey.yaml

@@ -33,9 +33,11 @@ spec:
       {{- end }}
       automountServiceAccountToken: {{ .Values.serviceAccount.automount }}
       serviceAccountName: {{ include "valkey.serviceAccountName" . }}
+      {{- if .Values.priorityClassName }}
+      priorityClassName: {{ .Values.priorityClassName | quote }}
+      {{- end }}
       securityContext:
       {{- toYaml .Values.podSecurityContext | nindent 8 }}
-      
       initContainers:
         - name: {{ .Chart.Name }}-init
           image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"

valkey/values.schema.json

@@ -290,6 +290,9 @@
                 }
             }
         },
+        "priorityClassName": {
+            "type": "string"
+        },
         "replicaCount": {
             "type": "integer"
         },

valkey/values.yaml

@@ -36,6 +36,8 @@ podSecurityContext:
   runAsUser: 1000
   runAsGroup: 1000
 
+priorityClassName: ""
+
 # Security context for the Valkey containers
 securityContext:
   capabilities:
@@ -315,4 +317,8 @@ metrics:
     #     increase(redis_evicted_keys_total{service="{{ include "valkey.fullname" . }}-metrics"}[5m]) > 0
     #   for: 1s
     #   labels:
-    #     severity: error
+    #     severity: error
+# Environment variables to inject into Valkey container
+env: {}
+  # Example:
+  # LOG_LEVEL: info