mariadb-operator VS mariadb-poc

Once you have learnt the basics I would recommend you to contribute to an open source operator like mariadb-operator: https://github.com/mariadb-operator/mariadb-operator

In this blog, we discuss the effective utilization of mariadb-operator to manage MariaDB instances in Kubernetes using CRDS, promoting a declarative approach instead of relying on imperative commands.

v0.0.16 release: https://github.com/mariadb-operator/mariadb-operator/releases/tag/v0.0.16

Refer to the documentation for further detail: https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/GALERA.md

I think I've managed to reproduce your issue using podman rootless KIND, but it does not have to do with Podman at all. It was some RBAC misconfiguration in the last version of the Helm chart that caused the controller to be unable to watch some resources on the Kubernetes API. I've released a v0.0.3 to fix this.

I'm quite happy to announce that, after months of work, I'm releasing today the second alpha version of mariadb-operator, a Kubernetes operator written in Go that enables you to run and operate MariaDB in a cloud native way. Forget about imperative commands, do everything declaratively using CRDs.

I've created an issue for this: https://github.com/mmontes11/mariadb-operator/issues/10

Lastly, regarding the Galera support, thanks for providing those resources. I already have a working PoC to setup Galera, but it will be worth checking if I am on the same page. The intention is supporting this feature as part of the upcoming releases of mariadb-operator, so stay tuned!