To run MySQL on Kubernetes you usually pick an operator: a controller that provisions the database, keeps replication healthy, fails over when the primary dies and takes backups. Several are actively maintained, and they differ in which MySQL they run, how they stay available and how far back you can restore.

We maintain CNMSQL, so we are not neutral. Every fact below comes from each project's own documentation, listed under Sources, and there is a full section on what CNMSQL cannot do. If something is wrong or out of date, open an issue.