openstack
/
openstack-helm-infra
Code Issues Proposed changes
openstack-helm-infra/mariadb-backup
History
Sergiy Markin 13c1d8cd38 [backups] Add throttlling of remote backups 
This PS adds a possibility to limit (to throttle) the number of
simultaneously uploaded backups while keeping the logic on the client
side using flag files on remote side. The main idea is to have an
ability to limit number of simultaneous remote backups upload sessions.

Change-Id: I5464004d4febfbe20df9cd41ca62ceb9fd6f0c0d
 		2023-12-18 20:39:45 +00:00
..
templates [backups] Add throttlling of remote backups 2023-12-18 20:39:45 +00:00
values_overrides [backups] Added staggered backups 2023-12-05 04:10:22 +00:00
Chart.yaml [backups] Add throttlling of remote backups 2023-12-18 20:39:45 +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 [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