openstack/openstack-helm-infra
Code Issues Proposed changes
7df8ebde19
openstack-helm-infra/mariadb-cluster
History
Sergiy Markin d0b3f1c1d2 [mariadb-operator] Fix mariadb TLS 
This PS fixed some imcompatibilities of inherited mariadb config with
docker-entrypoint.sh script that is now used to perform initial mariadb
nodes setup and mariadb-upgrade at startup.
Also added x509 requirement for root and audit users
connections.


Change-Id: Ic5ad2e692b64927fc73962fe0cc250a9d682114c
2024-01-08 17:43:17 +00:00
..
templates [mariadb-operator] Fix mariadb TLS 2024-01-08 17:43:17 +00:00
values_overrides [mariadb-operator] Mariadb-cluster chart 2023-11-29 21:51:48 -06:00
.helmignore [mariadb-operator] Mariadb-cluster chart 2023-11-29 21:51:48 -06:00
Chart.yaml [mariadb-operator] Fix mariadb TLS 2024-01-08 17:43:17 +00:00
README.rst [mariadb-operator] Mariadb-cluster chart 2023-11-29 21:51:48 -06:00
requirements.yaml [mariadb-operator] Mariadb-cluster chart 2023-11-29 21:51:48 -06:00
values.yaml [mariadb-operator] Fix mariadb TLS 2024-01-08 17:43:17 +00:00

README.rst

openstack-helm/mariadb

By default, this chart creates a 3-member mariadb galera cluster.

This chart depends on mariadb-operator chart.

The StatefulSets all leverage PVCs to provide stateful storage to /var/lib/mysql.

You must ensure that your control nodes that should receive mariadb instances are labeled with openstack-control-plane=enabled, or whatever you have configured in values.yaml for the label configuration:

kubectl label nodes openstack-control-plane=enabled --all