add posibility to define resource requests and limits in helm chart

Signed-off-by: Marius Stein <[email protected]>
opstree · Mar 1, 2021 · cec4f6c · cec4f6c
1 parent b0e2643
commit cec4f6c
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 0 deletions.
diff --git a/helm/templates/deployment.yaml b/helm/templates/deployment.yaml
@@ -45,6 +45,8 @@ spec:
         ports:
         - containerPort: {{ .Values.exporterPort }}
           protocol: TCP
+        resources:
+          {{- toYaml .Values.resources | nindent 12 }}
 {{- if .Values.serviceAccount.create }}
       serviceAccount: {{ include "prometheus-druid-exporter.fullname" . }}
       serviceAccountName: {{ include "prometheus-druid-exporter.fullname" . }}

diff --git a/helm/values.yaml b/helm/values.yaml
@@ -14,6 +14,18 @@ logFormat: json
 
 exporterPort: 8080
 
+resources: {}
+  # We usually recommend not to specify default resources and to leave this as a conscious
+  # choice for the user. This also increases chances charts run on environments with little
+  # resources, such as Minikube. If you do want to specify resources, uncomment the following
+  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
+  # limits:
+  #   cpu: 100m
+  #   memory: 128Mi
+  # requests:
+  #   cpu: 100m
+  #   memory: 128Mi
+
 security:
   enabled: false
   druidUser: admin