From 62f0fadffd14f7a6d8ac7251cd0abd09ecdf2a92 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6nke=20Liebau?= Date: Mon, 3 Jul 2023 08:03:14 +0000 Subject: [PATCH] Set resource limits for operator deployment (#376) For https://github.com/stackabletech/issues/issues/368 we need to set resource limits on all resources deployed by our helm charts. --- deploy/helm/superset-operator/values.yaml | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/deploy/helm/superset-operator/values.yaml b/deploy/helm/superset-operator/values.yaml index bc6734a8..6ac308db 100644 --- a/deploy/helm/superset-operator/values.yaml +++ b/deploy/helm/superset-operator/values.yaml @@ -30,17 +30,13 @@ securityContext: {} # runAsNonRoot: true # runAsUser: 1000 -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 +resources: + limits: + cpu: 100m + memory: 128Mi + requests: + cpu: 100m + memory: 128Mi nodeSelector: {}