aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/common/mariadb-init/values.yaml
AgeCommit message (Collapse)AuthorFilesLines
2022-04-29[COMMON][MARIABD] MariaDB ServiceMesh compatibilityAndreas Geissler1-0/+4
Update the port names of metrics and mariadb to match the istio requirements and update the timeouts. Fix mysql protocol setup for istio and update mariadb-init job to support istio sidecar communication. This is separated from a patch for CDS SM compatibility Issue-ID: OOM-2820 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I02c19c9fcfbd76a2cede0b924174ad81b45d719e
2020-11-21[COMMON][MARIADB-INIT] Uses new tpls for repos / imagesSylvain Desbureaux1-3/+0
This commit makes mariadb init template to use the new generator for repositories and images. As mariadb images are coming from dockerhub, we're using directly this repository. Issue-ID: OOM-2364 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I21e99fc4c7c4d968b393d27dfad2b51bcc5c2cfd
2020-11-18[COMMON/VID] Modified VID to use Shared DB.RPMishra1-0/+7
This change modifies VID to use the shared DB instance of mariadb. In addition, we create a mechanism in mariadb-init to allow a shared DB user to run a script after the DB has been created. The script can be passed as a configMap (as is the case with VID) or it can be a standalone script that is passed as a string. Issue-ID: OOM-1226 Change-Id: Ie51823338562a6fbe7472025d62cd4dba688168d Signed-off-by: RPMishra <rpmishra@aarnanetworks.com> Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-09-06[COMMON] Allow to initialize custom mariadb instanceKrzysztof Opasiak1-2/+11
Add the ability to use mariadb-init to create databases in any mariadb-galera instace not only the common one. Issue-ID: OPTFRA-800 Change-Id: Idfeacc9af49620378eb5b06ae3628f92e740cc65 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
2020-09-04[GENERAL] Use readiness container v3.0.1Sylvain Desbureaux1-2/+1
Readiness container v3.x and up are now present in ONAP main repository. They're also not using root user anymore and then script path has changed. Finally, "job_complete" script has been integrated in main "ready" script. As those changes are significant, we must upgrade all the components at once. Depends-On: I5afa83892043f4844afe12e61724a8d368a9f2e0 Issue-ID: OOM-2545 Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com> Change-Id: I0b4eb5dd86390273532d67d0a9696e1cfcadf110
2020-02-13Fix external secret name in mariadb-initKrzysztof Opasiak1-2/+2
mariadb-init chart should play nicely with mariadb-galera as it simplifies migration to common mariadb instance. Unfortunately after adding the support for common secret template I didn't pay enough attention to consistent naming convention and mariadb-galera and mariadb-init chart ended up being incompatible. To fix that let's just rename the mariadb-init chart config option to match exactly the one used in mariadb-galera chart. Issue-ID: OOM-2248 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I621804821292e2bd0b5b1dd3f010629d1cb5471f
2020-02-01[COMMON] Use common secret template in mariadb-initKrzysztof Opasiak1-2/+22
Use common secret template for all passwords that are used inside this chart. Issue-ID: OOM-2248 Change-Id: Ia94b87a4d0316a3d334fd492521be5a255c14b4e Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-12-21Use common secret template in mariadb-galeraKrzysztof Opasiak1-1/+1
Instead of defining the secret in some custom way let's use the common template (common.secret). To avoid some issues in ONAP components that depend on this chart let's do not remove for now the default username and password. We will do this when all services properly utylize secrets to store mariadb credentials. Issue-ID: OOM-2053 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I78e224299cccd9632192ee03a45cd077e6f0906f
2019-12-02[NBI] Use the common galera cluster of ONAPSylvain Desbureaux1-0/+87
Instead of having our "own" galera cluster, use the common one already proposed by OOM. If a local cluster is needed, you just need to set global.mariadbGalera.localCluster to True. Also create a common chart that create the needed values for the database. Change-Id: I9ad551b76a40732b4ab3fc34ba7cde6ca90fe432 Issue-ID: EXTAPI-348 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>