49c1174433
Also update chart_version.sh script which counts the number of commits since the BASE_VERSION if BASE_VERSION tag is found. If the tag doesn't exist it counts the number of commits since the beginning. So when we use for example 2025.1.0 as the BASE_VERSION but the tag 2025.1.0 is not yet created the version of the e.g. nova chart will be calculated as like 2025.1.563+<sha> and then when we create tag the nova version will be 2025.1.0+<sha> which is undesired. Lets use BASE_VERSION-<sha> if the tag is not found. Change-Id: I032e8269ab17b490898d190adaec5c282e96fa88
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