mariadb-operator
A Kubernetes operator that declaratively manages MariaDB through CRDs, covering replication and Galera topologies, MaxScale, physical and logical backups, and point-in-time recovery.
mariadb-operator runs MariaDB on Kubernetes from custom resources rather than imperative commands. It provisions standalone servers as well as highly available topologies built on asynchronous replication, Galera synchronous multi-master, or multi-cluster replication for multi-region deployments, disaster recovery, and blue-green upgrades, and it can deploy MaxScale as the proxy that load-balances requests and handles failover and switchover.
Backups can be physical (based on mariadb-backup and VolumeSnapshots) or logical (based on mariadb-dump), stored in S3-compatible storage, Azure Blob Storage, or PVCs, and binary log archiving enables point-in-time recovery. The operator also handles cluster-aware rolling updates, TLS certificate rotation, and Prometheus metrics. It’s released under the MIT license.
Community feedback
This space is for grounded, evaluable experience — versions used, environments, what you measured or observed, and how it behaves alongside other software. General impressions without supporting detail may be removed. Sign in to write one; posts are tied to a verified identity, not anonymous.