openstack/openstack-helm-infra
Code Issues Proposed changes
3edbef16f3
openstack-helm-infra/mariadb-backup
History
Vladimir Kozhukalov 672e488519 Update versions of all charts to 2024.2.0 
As per agreement with
https://docs.openstack.org/openstack-helm/latest/specs/2025.1/chart_versioning.html

Change-Id: Ia064d83881626452dc3c0cf888128e152692ae77
2024-12-18 11:05:10 -06:00
..
templates [backups] Add throttlling of remote backups 2023-12-18 20:39:45 +00:00
Chart.yaml Update versions of all charts to 2024.2.0 2024-12-18 11:05:10 -06:00
README.rst [mariadb-operator] Mariadb-cluster chart 2023-11-29 21:51:48 -06:00
values.yaml Update kubernetes-entrypoint image 2024-07-12 13:52:07 -05: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