Composing a Multi Database DBaaS from Open Source Kubernetes Operators
summary
Percona operators provide the DBaaS engine: automated deployments, HA, scaling, PITR and backups using PXB, PBM and PG BackRest, and uniform CRD APIs for MySQL (PXC/Galera, Group Replication), MongoDB (replica sets) and Postgres (Patroni). PMM ships for monitoring and cert-manager or injected secrets handle TLS; self‑signed certs are for dev. Gaps remain: build a self‑service portal, tenant isolation, secrets/Vault integration, restore testing, traffic failover and cost tagging. Cross‑site replication for Postgres lands in operator 1.2.
AI-written summary · about
chapters (12)
- 0:00Multi-database DBaaS intro
- 1:10Managed DBaaS challenges
- 4:44Production DBaaS features
- 6:50Kubernetes operators for DBaaS
- 9:16Percona operators overview
- 13:53High availability failover
- 14:56Backup strategies
- 18:45Disaster recovery
- 22:14Encryption in transit and at rest with operators
- 23:59Monitoring DBaaS
- 26:45Gaps in custom DBaaS
- 28:33Key takeaways
related talks
27mDatabase Infrastructure with Open Source Kubernetes Database Operators
31mOpen Source Databases on Kubernetes: Best Practices
27mDIY DBaaS with Percona Kubernetes Operators
19mPrivate DBaaS: Why you Need it, How to Build It
44mFrom a database in container to DBaaS on Kubernetes
01h 00mCross-Cloud Migrations With Databases on Kubernetes
36mFrom a Database in Container to DBaaS on Kubernetes
17mWhy Public Database as a Service is Prime for Open Source Distribution