aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/common/mariadb-galera
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2018-11-23 14:25:57 +0100
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2018-11-23 15:00:18 +0100
commitff702c70d4377e37a497dd916621d23419b061a9 (patch)
treec53f5c28510fb2456876dcf2493a5ddf56defbc7 /kubernetes/common/mariadb-galera
parenta7b2ee30e615a8567d953b644bc37ec07759fcdf (diff)
Use flavors for resources in mariadb-galera deploy
For Casablanca release, flavors have been set up for choosing the "right" resource requests and limits. Although the deployment is using the right way for that, mariadb-galera charts values.yaml was not. This commit makes values.yaml aligned with flavors. Change-Id: If51e8c5ad41dda7fa35c3aaaa58e60752094f133 Issue-ID: OOM-1528 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'kubernetes/common/mariadb-galera')
-rw-r--r--kubernetes/common/mariadb-galera/values.yaml21
1 files changed, 15 insertions, 6 deletions
diff --git a/kubernetes/common/mariadb-galera/values.yaml b/kubernetes/common/mariadb-galera/values.yaml
index 2305323ced..e4c6550f2b 100644
--- a/kubernetes/common/mariadb-galera/values.yaml
+++ b/kubernetes/common/mariadb-galera/values.yaml
@@ -117,12 +117,21 @@ externalConfig: {}
# Minimum memory for development is 2 CPU cores and 4GB memory
# Minimum memory for production is 4 CPU cores and 8GB memory
resources:
- limits:
- cpu: 2
- memory: 4Gi
- requests:
- cpu: 1
- memory: 2Gi
+ small:
+ limits:
+ cpu: 2
+ memory: 4Gi
+ requests:
+ cpu: 1
+ memory: 2Gi
+ large:
+ limits:
+ cpu: 2
+ memory: 4Gi
+ requests:
+ cpu: 1
+ memory: 2Gi
+ unlimited: {}
# Name for mariadb-galera cluster - should be unique accross all projects or other clusters
nameOverride: mariadb-galera