Add init container capability to initialize vmalert pod

VictoriaMetrics · Sep 4, 2024 · afb2f49 · afb2f49
1 parent cc042ce
commit afb2f49
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/charts/victoria-metrics-alert/templates/server-deployment.yaml b/charts/victoria-metrics-alert/templates/server-deployment.yaml
@@ -42,6 +42,10 @@ spec:
       {{- with ($app.imagePullSecrets | default .Values.global.imagePullSecrets) }}
       imagePullSecrets: {{ toYaml . | nindent 8 }}
       {{- end }}
+      {{- with $app.initContainers }}
+      initContainers:
+        {{- toYaml . | nindent 8 }}
+      {{- end }}
       containers:
         - name: vmalert
           {{- if $app.securityContext.enabled }}

diff --git a/charts/victoria-metrics-alert/values.yaml b/charts/victoria-metrics-alert/values.yaml
@@ -8,7 +8,7 @@ global:
   compatibility:
     openshift:
       adaptSecurityContext: "auto"
-      
+
 serviceAccount:
   # -- Specifies whether a service account should be created
   create: true
@@ -308,6 +308,8 @@ server:
     #         cpu: 1
     #         memory: 500Mi
     #       controlledResources: ["cpu", "memory"]
+  ## Additional initContainers to initialize the pod
+  initContainers: []
 
 serviceMonitor:
   # -- Enable deployment of Service Monitor for server component. This is Prometheus operator object