commit 8cbb3d9b964b774b1400df5d909913b669c2a243
author Andreas Geissler <andreas-geissler@telekom.de> Tue Mar 12 16:44:56 2024 +0100
committer Andreas Geissler <andreas-geissler@telekom.de> Thu Mar 14 13:45:13 2024 +0000
tree ee3efa1ba9268b223a99cf6822d0b4806d27e89c
parent 9468364310a767b4d68f35a94f15e79ff38c5908

[COMMON] Harmonize resource settings, Part 2

Some settings are still wrongly interpreted (e.g. 0.02Gi)
Therefor they are changed to non-floating numbers (e.g. 20Mi)

Issue-ID: OOM-3273

Change-Id: Icc88dead1ac5b1df8629d6adcc438a739e20522e
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>

kubernetes/common/elasticsearch/values.yaml

diff --git a/kubernetes/common/elasticsearch/values.yaml b/kubernetes/common/elasticsearch/values.yaml
index e1c8f72..7851f28 100644
--- a/kubernetes/common/elasticsearch/values.yaml
+++ b/kubernetes/common/elasticsearch/values.yaml
@@ -95,10 +95,10 @@
   ## resources, such as Minikube.
   limits: {}
   #   cpu: "100m"
-  #   memory: "0.1Gi"
+  #   memory: "100Mi"
   requests:
     cpu: "25m"
-    memory: "0.2Gi"
+    memory: "200Mi"
 ## Elasticsearch coordinating-only container's liveness and readiness probes
 ## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
 ##