openstack/openstack-helm
Code Issues Proposed changes
ff61c50dcc
openstack-helm/mariadb
History
Alan Meadows d9942320b5 fix requirements to only require common
2016-11-30 17:11:15 -08:00
..
templates remove duplicate mariadb service 2016-11-30 15:36:54 -08:00
.helmignore Adding MariaDB 2016-11-18 16:34:36 +01:00
Chart.yaml Adding MariaDB 2016-11-18 16:34:36 +01:00
README.md Refactor mariadb now that rbd PVCs can be leveraged 2016-11-23 13:26:08 -08:00
requirements.lock fix requirements to only require common 2016-11-30 17:11:15 -08:00
requirements.yaml aic-helm normalization 2016-11-29 16:20:06 -08:00
values.yaml use beta even in 1.4 2016-11-30 16:16:42 -08:00

README.md

aic-helm/mariadb

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

PetSets would be ideal to use for this purpose, but as they are going through a transition in 1.5.0-beta.1 and not supported by Helm 2.0.0 under their new name, StatefulSets, we have opted to leverage helms template generation ability to create Values.replicas * POD+PVC+PV resources. Essentially, we create a mariadb-0, mariadb-1, and mariadb-2 Pod and associated unique PersistentVolumeClaims for each. This removes the previous daemonset limitations in other mariadb approaches.

You must ensure that your control nodes that should receive mariadb instances are labeled with openstack-control-plane=enabled:

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

We will continue to refine our labeling so that it is consistent throughout the project.