Martin Montes

[v0.0.31](https://github.com/mariadb-operator/mariadb-operator/releases/tag/v0.0.31) has been released with this fix. Please follow [this guide ](https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/UPGRADE_v0.0.31.md)to upgrade.

@0xmeyer thanks for the detailed report and helping with the troubleshooting! Much appreciated 🙏🏻

Hey there @pschiffe ! Thanks for bringing this up. The root cause of this problem is that, by default, the `Secrets` reconciled by the operator set a reference to the...

> Readiness probe failed: Error 1045 (28000): access denied for user 'root'@'localhost' (using password: YES) This means that the `Secret` that holds the root password differs from the root password...

Startup probes are now supported (thanks @vixns ): - https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/CONFIGURATION.md#probes And next release we will be working on `PhysicalBackups`, which partially addresses PITR

@AayushVinayDev it would be great if you could add a test to prove that this functionallity works as expected. Also, make sure you rebase with `main`.

Hey there ! Thanks for reporting. I would check whether the `monitoring@%`user is available on the MariaDB server side, and also attempt to connect manually providing its password. There is...

Hey there @iammuho ! Thanks for bringing this up and investigate this. The operator defaults the `SecurityContext` of `MaxScale`' s `StatefulSet` to: ```yaml securityContext: fsGroup: 996 runAsGroup: 996 runAsNonRoot: true...

Please, fill the issue template and provide a description of your issue. In this case, a definition of the reconciled `Pods`.

> I can't develop and test any integration test in these conditions, is there a way to run a solo test ? @mmontes11 Hey @vixns ! Sorry to see you...