summaryrefslogtreecommitdiffstats
path: root/kubernetes/common
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2021-05-05 17:16:57 +0200
committerKrzysztof Opasiak <k.opasiak@samsung.com>2021-05-06 13:27:16 +0000
commit4d04706a2295529efbc265091979971dc90c8382 (patch)
tree204849ddd66bda90cde18e3121b1c70e4dd00925 /kubernetes/common
parent2ed34c50cd9b6655ffc24b759a14c4c41d3fcf2f (diff)
[COMMON][MARIADB] Give higher requests/limits
With stability tests, we see that mariadb gets OOM killed and has some CPU throttling. Putting higher limits in order to make it no happen. Scaling also replicas from VFC and APPC db from 3 to 1. Issue-ID: INT-1883 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I2699b34ac5fcaa805c6fc01592c5a5f607b17fae
Diffstat (limited to 'kubernetes/common')
-rw-r--r--kubernetes/common/mariadb-galera/values.yaml12
1 files changed, 6 insertions, 6 deletions
diff --git a/kubernetes/common/mariadb-galera/values.yaml b/kubernetes/common/mariadb-galera/values.yaml
index 79b1cb2933..0991031939 100644
--- a/kubernetes/common/mariadb-galera/values.yaml
+++ b/kubernetes/common/mariadb-galera/values.yaml
@@ -478,18 +478,18 @@ flavor: small
resources:
small:
limits:
- cpu: 500m
- memory: 2.5Gi
+ cpu: 1
+ memory: 4Gi
requests:
- cpu: 100m
- memory: 750Mi
+ cpu: 500m
+ memory: 2Gi
large:
limits:
cpu: 2
- memory: 4Gi
+ memory: 6Gi
requests:
cpu: 1
- memory: 2Gi
+ memory: 3Gi
unlimited: {}
## MariaDB Galera containers' liveness and readiness probes