[COMMON] Harmonize resource settings
Update all resource settings to the kubernetes recommended
normalized form. Fix ReadinessCheck resource limits.
Issue-ID: OOM-3273
Change-Id: Ie10903b801e4dc1689bcec092162d711a431a7a6
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
diff --git a/kubernetes/common/elasticsearch/components/curator/values.yaml b/kubernetes/common/elasticsearch/components/curator/values.yaml
index 62964ff..0a5080e 100644
--- a/kubernetes/common/elasticsearch/components/curator/values.yaml
+++ b/kubernetes/common/elasticsearch/components/curator/values.yaml
@@ -123,11 +123,11 @@
# 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
+ # cpu: "100m"
+ # memory: "0.1Gi"
requests: {}
- # cpu: 100m
- # memory: 128Mi
+ # cpu: "100m"
+ # memory: "0.1Gi"
priorityClassName: ""
# extraVolumes and extraVolumeMounts allows you to mount other volumes
# Example Use Case: mount ssl certificates when elasticsearch has tls enabled
diff --git a/kubernetes/common/elasticsearch/components/data/values.yaml b/kubernetes/common/elasticsearch/components/data/values.yaml
index 1dc9ab8..a0dad56 100644
--- a/kubernetes/common/elasticsearch/components/data/values.yaml
+++ b/kubernetes/common/elasticsearch/components/data/values.yaml
@@ -105,11 +105,11 @@
## choice for the user. This also increases chances charts run on environments with little
## resources, such as Minikube.
limits: {}
- # cpu: 100m
- # memory: 128Mi
+ # cpu: "100m"
+ # memory: "0.1Gi"
requests:
- cpu: 25m
- memory: 1152Mi
+ cpu: "25m"
+ memory: "1.1Gi"
## Elasticsearch data container's liveness and readiness probes
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
##
diff --git a/kubernetes/common/elasticsearch/components/master/values.yaml b/kubernetes/common/elasticsearch/components/master/values.yaml
index a2ec7b9..f4ac74e 100644
--- a/kubernetes/common/elasticsearch/components/master/values.yaml
+++ b/kubernetes/common/elasticsearch/components/master/values.yaml
@@ -108,13 +108,13 @@
## choice for the user. This also increases chances charts run on environments with little
## resources, such as Minikube.
limits:
- cpu: 250m
- memory: 1536Mi
- # cpu: 100m
- # memory: 128Mi
+ cpu: "250m"
+ memory: "1.5Gi"
+ # cpu: "100m"
+ # memory: "0.1Gi"
requests:
- cpu: 5m
- memory: 310Mi
+ cpu: "5m"
+ memory: "0.3Gi"
## Elasticsearch master-eligible container's liveness and readiness probes
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
##
diff --git a/kubernetes/common/elasticsearch/values.yaml b/kubernetes/common/elasticsearch/values.yaml
index c3352ae..e1c8f72 100644
--- a/kubernetes/common/elasticsearch/values.yaml
+++ b/kubernetes/common/elasticsearch/values.yaml
@@ -94,11 +94,11 @@
## choice for the user. This also increases chances charts run on environments with little
## resources, such as Minikube.
limits: {}
- # cpu: 100m
- # memory: 128Mi
+ # cpu: "100m"
+ # memory: "0.1Gi"
requests:
- cpu: 25m
- memory: 256Mi
+ cpu: "25m"
+ memory: "0.2Gi"
## Elasticsearch coordinating-only container's liveness and readiness probes
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
##