openstack/openstack-helm-infra
Code Issues Proposed changes
cf4a143e1b
openstack-helm-infra/mariadb-backup
History
Vladimir Kozhukalov 55177a6a67 Add 2024.1 overrides 
Depends-On: Iadc9aec92b756de2ecfcb610e62c15bdbad4bb9e
Change-Id: Icf98f9af863f60fa93ff70d2e8256810bed2b9f9
2024-03-28 13:57:03 -05:00
..
templates [backups] Add throttlling of remote backups 2023-12-18 20:39:45 +00:00
values_overrides Add 2024.1 overrides 2024-03-28 13:57:03 -05:00
Chart.yaml Add 2024.1 overrides 2024-03-28 13:57:03 -05: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 [backups] Add throttlling of remote backups 2023-12-18 20:39:45 +00:00

README.rst

openstack-helm/mariadb-backup ======================

By default, this chart creates a mariadb-backup cronjob that runs in a schedule in order to create mysql backups.

This chart depends on mariadb-cluster chart.

The backups are stored in a PVC and also are possible to upload then to a remote RGW container.

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