State of this project

[nick4fake]

Firstly, I am realy greateful for this operator. It is the only MySQL operator with support for multiple DBs/users.

What is the current state of the project? After spending a day trying to work with it (simply following guide), I have found the following issues:

• MySQL 8.0 doesn't work (possible due to this bug: https://github.com/bitpoke/mysql-operator/issues/742), the same config with 5.7 works without any issues mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (OS errno 13 - Permission denied)
• There haven't been any new tags for quite a while (https://github.com/bitpoke/mysql-operator/issues/840). Using 0.6.2 is impossible on new clusters due to API version mismatch. ghcr.io/ksmartdata/mysql-operator#0.7.3 has helped to actually set it up, though I still needed to use orchestrator 0.6.2 (possibly due to them building image incorrectly)
• No default configs actually work. Deploying operators requires pointing to master branch (instead of Helm repo) and using multiple mismatching versions (master for helm, 0.7.3. for operator and sidecars, 0.6.2 for orchestrators)
• Even creating a user has failed: https://github.com/bitpoke/mysql-operator/issues/719

Once again, this is a great project, though I am confused: is there anyone using it in production? Is it safe to use, or it is just a demo project?

[Sea-you]

We are using the operator on a bigger scale for years, and despite some small stuff that has been fixed over the years, it's an excellent project.