mariadb-operator
mariadb-operator is a Kubernetes operator that automates deployment, management, and operation of MariaDB databases in cloud-native environments. It provides declarative management through CRDs, supporting multiple HA topologies, automated backups, replication, and multi-cluster deployments.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | mariadb-operator/mariadb-operator |
| Owner | mariadb-operator |
| Primary language | Go |
| License | MIT — OSI-approved |
| Stars | 988 |
| Forks | 180 |
| Open issues | 190 |
| Latest release | mariadb-operator-crds-26.6.0 (2026-06-06) |
| Last updated | 2026-07-08 |
| Source | https://github.com/mariadb-operator/mariadb-operator |
What mariadb-operator is
Go-based Kubernetes operator using CRDs to manage MariaDB lifecycle, including provisioning, scaling, backup/restore (physical and logical), replication (async and Galera), MaxScale integration, TLS management, and Point-In-Time Recovery. Integrates with cert-manager, prometheus-operator, and VolumeSnapshots.
Get the mariadb-operator source
Clone the repository and explore it locally.
git clone https://github.com/mariadb-operator/mariadb-operator.gitcd mariadb-operator# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires persistent volume provisioners with snapshot support for backup and restore; verify storage class capabilities before deployment.
- Plan for initial Kubernetes skill investment: operators, CRDs, networking, and RBAC configuration are non-trivial for teams new to cloud-native databases.
- Test upgrade paths carefully—documentation warns against skipping intermediate versions; establish upgrade runbooks before production.
- HA topology choice (async replication vs. Galera) impacts consistency, latency, and failure modes; evaluate against specific RPO/RTO targets.
- Backup strategy must account for network bandwidth, storage quota, encryption key management, and retention compliance.
When to avoid it — and what to weigh
- Non-Kubernetes database deployments — This operator is purpose-built for Kubernetes; it adds no value for traditional VM or bare-metal MariaDB installations.
- Minimal operational expertise available — Effective use requires understanding of Kubernetes operators, CRDs, storage classes, networking, and MariaDB replication topology. Misconfiguration can lead to data loss or service disruption.
- Strict vendor lock-in avoidance requirements — Tight coupling to Kubernetes API and operator patterns may make future migration to non-Kubernetes environments or different operators more complex.
- Need for real-time, sub-second failover SLA — While HA topologies are supported, Kubernetes scheduling, pod restart times, and operator reconciliation loops may not meet ultra-low-latency failover requirements.
License & commercial use
Licensed under MIT (MIT License), a permissive OSI-approved license.
MIT license permits commercial use, modification, and distribution without requiring source code disclosure or royalty payments. No formal support contract, SLA, or commercial terms evident from repository. Treat as community-supported; clarify support expectations before production deployment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | High |
Automated TLS certificate management via cert-manager; root password rotation via Secret updates; supports encryption at rest via VolumeSnapshot mechanisms and backup encryption (SSE-C). Validation webhooks provide CRD immutability. RBAC and network policies must be configured separately. Distroless multi-arch images reduce attack surface. No public security audit, CVE, or incident history provided in data; conduct threat modeling for sensitive workloads.
Alternatives to consider
Percona Kubernetes Operator for MySQL
Comparable Kubernetes operator for MySQL/Percona Server with HA, backups, and declarative management; stronger vendor support but primarily MySQL-focused.
Helm charts + manual MariaDB Galera deployment
Lower abstraction level; more control but requires custom lifecycle scripting for backups, upgrades, and failover; higher operational burden.
CloudSQL (GCP), RDS (AWS), Azure Database for MySQL
Managed database services eliminate operator complexity and Kubernetes dependency; higher cost, potential vendor lock-in, less on-premises flexibility.
Build on mariadb-operator with DEV.co software developers
Explore mariadb-operator's capabilities, assess your Kubernetes readiness, and let's design a cloud-native database strategy for your infrastructure.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
mariadb-operator FAQ
Does the operator handle backup and restore automatically?
What HA topologies are supported?
Is this suitable for production?
How do I upgrade the operator and MariaDB clusters?
Software developers & web developers for hire
Adopting mariadb-operator is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.
Ready to modernize your MariaDB operations?
Explore mariadb-operator's capabilities, assess your Kubernetes readiness, and let's design a cloud-native database strategy for your infrastructure.