Stop developments 💔🖖

[blaqkube]

Stop developments 💔🖖

Hello @hubwoop . Thank you for the comment! We have retired the project due to the fact it is a lot of work to get it right and even more to maintain. We have decided to move to a MySQL managed service instead. I'll document it:

• If you are interested with the documentation, you can check the docs directory.
• If you are looking for a MySQL operator, check presslabs/mysql-operator or percona/percona-xtradb-cluster-operator. That would not fit our requirements but they are 2 very active and nice projects. There are others but not like these
• If you think that is a bad idea to leave the project here, do not hesitate to tell

I'll leave this issue open for now, time to remove the missing links and document the current position.

[hubwoop]

Hey @blaqkube thanks for the fast answer, albeit the content being very sad 😢.
Your project looks very promising to me!!! I wanted to evaluate it as a solution for creating many databases for wordpress installations on top of kubernetes. Currently, each wordpress deployment has its own mysql-database/mariadb pod which seems wasteful and backups are a nightmare. I don't think the other operators (like the ones you linked) cover this use case as good as this one and your crds look like a great api!

Is the operator - as is - stable enough to use it in our hobby cluster? If it's working right now, I wouldn't discard it too fast!

It is working and yes, we could deploy many databases in one instance. You would have to deploy it manually since we've removed it from operatorHub.io . Biggest concerns to us were #149 and #150. Plus that is was not ready for production, i.e. no HA yet. In your case, there might be other concerns:

• It is MySQL CE, not MariaDB. It should not be a lot of work to adapt it but, still, not tonight for sure
• The cloning/restore is per instance, not per database so it might also require some work if you need it.

If you are interested to discuss the problems you will face, email me gregory at blaqkube dot io . I would have to understand how sort of architecture you have (is it on-premises or not) and your requirements. This is an awesome project but the true challenge is that you have to keep up with operator-sdk (1.0 had been hard), kubernetes (1.15, 1.16 and 1.17 have been tough) and MySQL. They all move at a good pace so keeping up is sort of a challenge... And we do not have to maintain a legacy set of releases.