Well, I'm content with the initial version, so removing WIP. I have not done much of manual e2e testing though to be honest :)

I have not done much of manual e2e testing though to be honest :)

I'm happy enough with the automation you've built. Manual e2e testing will be conducted at the end of the release, planning to automate this at some point covering Helm installation.

Will hold the merge until manual e2e testing is performed, since the chart will be automatically released after merging to main:

This will be included in 25.08.0 after I make the adaptations mentioned above.

Hi team

Thank you for inviting me to share feedback!

I think it would be valuable to include a backup system, even in the first version of the Helm chart. Backups are critical for production use, and having even a basic option (e.g., scheduled backups to S3 or local PVC) would greatly help users adopt the chart safely from the start.

Happy to discuss this further or help implement it if needed!

Thanks again for your hard work on this project.

If you want, I can also help you:
Draft a technical breakdown of a lightweight S3 backup implementation for MariaDB Helm charts.

@Amir-Ghojavand FYI we have supported PhysicalBackups in this release. They have been merged to main but not released yet. They are documented here:
https://github.com/mariadb-operator/mariadb-operator/blob/release-25.08/docs/PHYSICAL_BACKUP.md

no i mean backup for the helm chart not the crd of pbc

@Amir-Ghojavand I've added backups templating with the corresponding test. Backup is a secondary resource like db/user/grant, so we will not impose it by default. Yet, a consumer will be able to configure it if need be.

@mmontes11 I don't remember saying it, but I kinda intend to leave Chart.yaml (at least versions lol) and helm-docs stuff to you so you could polish it up to your liking and vision.

I don't remember saying it, but I kinda intend to leave Chart.yaml (at least versions lol) and helm-docs stuff to you so you could polish it up to your liking and vision.

Sure thing, will take care of the CI related stuff before the release. Will also add support for PhysicalBackup, the same way you did for Backup