bitpoke/mysql-operator
Asynchronous MySQL Replication on Kubernetes using Percona Server and Openark's Orchestrator. observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3222
- days_rel: n/a
- days_push: 755
- n_releases_24m: 0
Adoption not part of the score
1091 stars · 276 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Kubernetes operator that deploys and manages highly available MySQL clusters using Percona Server and Openark's Orchestrator for asynchronous replication. It automates cluster provisioning, scheduled and on-demand backups, point-in-time recovery, and cross-cluster cloning.
Use cases
- run a highly available mysql cluster on kubernetes
- automate mysql backups and point-in-time recovery
- deploy mysql clusters declaratively with a kubernetes operator
- set up asynchronous mysql replication with orchestrator
- clone a mysql cluster across kubernetes clusters
- schedule recurrent mysql backups in kubernetes
When to choose
- you run workloads on Kubernetes and want MySQL clusters managed declaratively
- you need built-in backups, point-in-time recovery, and failover without manual scripting
- you want asynchronous replication topology managed by Orchestrator
- you are deploying WordPress or similar apps that need a cloud-native MySQL backend
When to avoid
- you are not running Kubernetes - a plain MySQL install or managed database is simpler
- you need synchronous (Galera-style) replication rather than asynchronous
- you need a database other than MySQL/Percona Server
- you require very active development or guaranteed timely community support - the project is in maintenance mode with best-effort issue responses
Facets
service · maturity maintenance
database deployment backup monitoring container-orchestration databases self-hosted go cloud self-hosted mysql-operator kubernetes-operator percona-server orchestrator mysql-cluster point-in-time-recovery high-availability asynchronous-replication devops containers kubernetes docker
10 sources
- readme: https://github.com/bitpoke/mysql-operator · fetched 2026-08-28 · aa9418ac079f
- homepage: https://www.bitpoke.io/docs/mysql-operator/getting-started/ · fetched 2026-08-29 · 8879504e1d0c
- site_page: https://www.bitpoke.io/docs/app-for-wordpress · fetched 2026-08-29 · 27ad759df8dc
- site_page: https://www.bitpoke.io/docs/mysql-operator · fetched 2026-08-29 · 94a701bdb515
- site_page: https://www.bitpoke.io/about-us · fetched 2026-08-29 · a71b17ab1e4d
- site_page: https://www.bitpoke.io/docs/app-for-wordpress/overview · fetched 2026-08-29 · 19a80ed4797a
- site_page: https://www.bitpoke.io/docs/app-for-wordpress/installation/prerequisites · fetched 2026-08-29 · c78c66fd542b
- site_page: https://www.bitpoke.io/docs/app-for-wordpress/installation/authentication · fetched 2026-08-29 · 60a306dbdc44
- site_page: https://www.bitpoke.io/docs/app-for-wordpress/installation/install · fetched 2026-08-29 · c5207e4e5113
- site_page: https://www.bitpoke.io/pricing · fetched 2026-08-29 · fa403fb41f37
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| bitpoke/mysql-operator | main | 23 |
For agents
markdown · JSON · MCP: product_card(name="bitpoke/mysql-operator")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem