openstack
/
openstack-helm-infra
Code Issues Proposed changes
openstack-helm-infra/mariadb-backup
History
Sergiy Markin 4a95f75b6b [backups] Added staggered backups 
This PS adds staggered backups possibility by adding anti-affinity rules
to backups cronjobs that can be followed across several namespaces to
decrease load on remote backup destination server making sure that at
every moment in time there is only one backup upload is in progress.

Change-Id: If49791f866a73a08fb98fa0e0b4854042d079c66
 		2023-12-05 04:10:22 +00:00
..
templates [backups] Added staggered backups 2023-12-05 04:10:22 +00:00
values_overrides [backups] Added staggered backups 2023-12-05 04:10:22 +00:00
Chart.yaml [backups] Added staggered backups 2023-12-05 04:10:22 +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] Mariadb-cluster chart 2023-11-29 21:51:48 -06: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