oracle/mysql-operator — explained in plain English
Analysis updated 2026-07-25 · repo last pushed 2021-05-28
Run a self-healing MySQL database on Kubernetes that restarts automatically if a server crashes.
Automatically scale your database cluster up or down during traffic spikes.
Keep a web app database online without dedicating staff to constant manual maintenance and repair.
| oracle/mysql-operator | oracle/terraform-provider-oci | cosmtrek/mindwalk | |
|---|---|---|---|
| Stars | 860 | 865 | 889 |
| Language | Go | Go | Go |
| Last pushed | 2021-05-28 | 2026-07-15 | — |
| Maintenance | Dormant | Active | — |
| Setup difficulty | hard | moderate | easy |
| Complexity | 4/5 | 4/5 | 2/5 |
| Audience | ops devops | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a running Kubernetes cluster and the project is archived/discontinued, so setup is not recommended.
The mysql-operator project was a tool designed to run MySQL databases on Kubernetes with minimal manual effort. In simple terms, it automated the hard parts of keeping a database running: if something broke, the system tried to fix itself. This meant it could automatically restart failed database instances and grow or shrink the database cluster as needed. At a high level, MySQL is one of the most popular database systems in the world, powering the storage behind countless websites and applications. Kubernetes is a platform that automates the deployment and scaling of containerized applications. This project connected the two. Rather than having engineers manually configure, monitor, and repair database servers, it used custom logic to treat the database like a self-managing service. This would be useful for engineering teams running applications that need reliable data storage without dedicating staff to constant database maintenance. For example, a startup running a web app could use it to ensure their database stays online even if a server crashes, and to add more capacity during traffic spikes. It takes care of operational concerns like backups, replication, and failover so the team can focus on building features. However, this version of the project has been discontinued. The repository is now archived and will not receive further updates or security patches. The maintainers have moved development to a new location, and anyone looking to use or contribute to the project should look there instead.
A tool that automated running MySQL databases on Kubernetes, handling restarts, scaling, backups, and failover automatically. The project is archived and discontinued, development has moved elsewhere.
Mainly Go. The stack also includes Go, Kubernetes, MySQL.
Dormant — no commits in 2+ years (last push 2021-05-28).
No license information is mentioned in the explanation, so the licensing terms for this archived project are unknown.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.