DIY DBaaS with Percona Kubernetes Operators
summary
Provides automated DBaaS primitives: Percona XtraDB Cluster Operator and Percona Server for MongoDB Operator deployable via kubectl, Helm or a CLI, runnable on EKS/GKE/AKS/OpenShift. Claims include a three-node default cluster for HA, automatic minor upgrades, scheduled backups to S3-compatible storage, scaling up/down, self-healing when pods fail, HAProxy (or ProxySQL) routing, encryption in transit and at rest with KMS/vault integration, and roadmapped PITR and MongoDB sharding.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:11Kubernetes what?
- 1:44Operator what?
- 4:10Is Kubernetes Ready for Databases?
- 6:17Why do we focus on Kubernetes
- 8:17Cloud-like experience
- 9:30Why do we focus on Operators
- 10:42When to choose Kubernetes
- 11:30The outcome
- 12:12When NOT to choose Kubernetes
- 13:04How Operator Works
- 14:06Percona Kubernetes Operator for Xtra Cluster
- 18:00Deployment
- 19:11What is happening here
- 20:03storage
- 20:53Let's discuss
- 22:08Proxy
- 23:16More features
- 23:51Encryption
- 24:44If you do not like YAML
- 25:12Percona Kubernetes Operator for Percona Serverf MongoDB
- 26:13Resources
related talks
27mDatabase Infrastructure with Open Source Kubernetes Database Operators
30mComposing a Multi Database DBaaS from Open Source Kubernetes Operators
19mPrivate DBaaS: Why you Need it, How to Build It
44mFrom a database in container to DBaaS on Kubernetes
31mOpen Source Databases on Kubernetes: Best Practices
36mFrom a Database in Container to DBaaS on Kubernetes
01h 00mCross-Cloud Migrations With Databases on Kubernetes
23mRunning MySQL on K8s. Deployment, Scaling, Backups and advanced configuration