openstack/openstack-helm-infra
Code Issues Proposed changes
00334a7f8a
openstack-helm-infra/mariadb
History
Nafiz Haider 6ee06562c8 Re-enable "feat(tls): Change Issuer to ClusterIssuer"" 
This reverts commit 8a79d7c51b.

Reason for revert: resolved bug with cluster issuer versioning

Co-authored-by: Sangeet Gupta <sg774j@att.com>

Change-Id: I047cbfaa5aa9e7285a23e603074429180495557d
2021-02-24 20:50:24 +00:00
..
files Fix ipv6 address cannot be parsed in mariadb-ingress pod 2020-05-06 01:53:36 +00:00
templates Fix MariaDB backup script 2020-09-30 22:01:22 +00:00
values_overrides Re-enable "feat(tls): Change Issuer to ClusterIssuer"" 2021-02-24 20:50:24 +00:00
.helmignore MariaDB: Move chart to openstack-helm-infra 2018-09-04 18:57:53 -05:00
Chart.yaml Re-enable "feat(tls): Change Issuer to ClusterIssuer"" 2021-02-24 20:50:24 +00:00
README.rst MariaDB: Move chart to openstack-helm-infra 2018-09-04 18:57:53 -05:00
requirements.yaml Change helm-toolkit dependency version to ">= 0.1.0" 2020-09-24 12:19:28 -05:00
values.yaml Update to container image repo k8s.gcr.io 2020-12-07 19:34:09 +00:00

README.rst

openstack-helm/mariadb

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

This chart leverages StatefulSets, with persistent storage.

It creates a job that acts as a temporary standalone galera cluster. This host is bootstrapped with authentication and then the WSREP bindings are exposed publicly. The cluster members being StatefulSets are provisioned one at a time. The first host must be marked as Ready before the next host will be provisioned. This is determined by the readinessProbes which actually validate that MySQL is up and responsive.

The configuration leverages xtrabackup-v2 for synchronization. This may later be augmented to leverage rsync which has some benefits.

Once the seed job completes, which completes only when galera reports that it is Synced and all cluster members are reporting in thus matching the cluster count according to the job to the replica count in the helm values configuration, the job is terminated. When the job is no longer active, future StatefulSets provisioned will leverage the existing cluster members as gcomm endpoints. It is only when the job is running that the cluster members leverage the seed job as their gcomm endpoint. This ensures you can restart members and scale the cluster.

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