Open Source Databases on Kubernetes: Best Practices
summary
Percona provides Kubernetes operators for MySQL (Group Replication), XtraDB/Galera, MongoDB and PostgreSQL that implement use an operator as the primary best practice, automating reconciliation, HA, backups and DR. Operators enforce no data loss over availability policies, offer migration paths like cross‑cluster replication and restore-from-physical-backup, and perform autotune buffers from container limits (e.g., InnoDB buffer pool, WiredTiger cache). Built-in troubleshooting tooling, PGBackRest/PgBouncer packaging, and open repos are part of the solution.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:46Why use Kubernetes
- 1:50Best Practices
- 2:56Know Yourself
- 4:47Automation
- 6:28Operators
- 8:49Features
- 9:36Availability
- 11:49Performance
- 13:27Troubleshooting
- 15:57Reliability
- 17:30Summary
- 18:33Paraconic Humanity
- 19:39Community
- 20:10Questions
- 20:20Acceptance tests
- 21:34Autotuning
- 22:06Buffer pool size
- 24:24Data layer abstraction
related talks
27mDatabase Infrastructure with Open Source Kubernetes Database Operators
30mComposing a Multi Database DBaaS from Open Source Kubernetes Operators
27mDIY DBaaS with Percona Kubernetes Operators
01h 00mCross-Cloud Migrations With Databases on Kubernetes
34mDatabases on Kubernetes
50mThe hell of SQL DBs on Kubernetes versus the promise of operators
44mFrom a database in container to DBaaS on Kubernetes
53mState of Open Source Databases and how Percona Contributes