aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/so/components/so-mariadb/values.yaml
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2020-10-30 14:32:03 +0100
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2020-11-02 16:49:49 +0000
commitd055a17d87b9e6bbfde51f523eea1838bc6b40dd (patch)
tree2e2a04467c315f0dd25363602fbae6c5f98bc132 /kubernetes/so/components/so-mariadb/values.yaml
parent92b606b267cf7e48336f3383bfb459253052c88c (diff)
[SO] Use readiness chart
Some SO components are using readiness check init container. In "gating" mode, so image and readiness image are not coming from the same repository. By using readinessCheck charts, we can control that. Issue-ID: OOM-2617 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I44a4e9daf72d1a42d3d84b6d56b588cd7d44fb08
Diffstat (limited to 'kubernetes/so/components/so-mariadb/values.yaml')
-rwxr-xr-xkubernetes/so/components/so-mariadb/values.yaml7
1 files changed, 6 insertions, 1 deletions
diff --git a/kubernetes/so/components/so-mariadb/values.yaml b/kubernetes/so/components/so-mariadb/values.yaml
index 9ecf3b0ca6..809dff77a7 100755
--- a/kubernetes/so/components/so-mariadb/values.yaml
+++ b/kubernetes/so/components/so-mariadb/values.yaml
@@ -24,7 +24,7 @@ global:
readinessImage: onap/oom/readiness:3.0.1
ubuntuInitRepository: registry.hub.docker.com
mariadbGalera:
- nameOverride: mariadb-galera
+ nameOverride: &mariadbName mariadb-galera
serviceName: mariadb-galera
servicePort: "3306"
migration:
@@ -33,6 +33,11 @@ global:
dbPort: 3306
dbUser: root
dbPassword: secretpassword
+
+readinessCheck:
+ wait_for:
+ - *mariadbName
+
#################################################################
# Secrets metaconfig
#################################################################