[MARIADB][SO] Connect MariaDB Galera via master node
To avoid "lock" situations all clients of the mariadb-galera
cluster should use the "primary" service, which connects
to the master node.
This service is provided by the mariadb-operator.
Additionally for SO the bugfix for "local" DB configuration
is fixed.
Additionally missing readiness checks added to so-cnfm-lcm and
so-etsi-nfvo-ns-lcm to wait for the DB job to complete
Issue-ID: OOM-3261
Issue-ID: OOM-2697
Change-Id: I3d44f8b6d84d112c0271bfccebc4fa533c4e6aff
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
diff --git a/kubernetes/so/components/so-admin-cockpit/values.yaml b/kubernetes/so/components/so-admin-cockpit/values.yaml
index e316456..2da7dd0 100644
--- a/kubernetes/so/components/so-admin-cockpit/values.yaml
+++ b/kubernetes/so/components/so-admin-cockpit/values.yaml
@@ -31,6 +31,8 @@
persistence:
mountPath: /dockerdata-nfs
mariadbGalera:
+ # flag to enable the DB creation via mariadb-operator
+ useOperator: true
service: mariadb-galera
servicePort: '3306'
@@ -67,6 +69,15 @@
image: onap/so/so-admin-cockpit:1.9.0
pullPolicy: Always
+# Local mariadb galera instance default name
+mariadb-galera:
+ nameOverride: so-mariadb-galera
+ service:
+ internalPort: 3306
+ mariadbOperator:
+ galera:
+ enabled: false
+
db:
userName: so_user
userPassword: so_User123