Lessons Learned from Building a Database Operator
summary
A Kubernetes operator that runs MongoDB is presented with a control plane (ops manager + operator) and a data plane (mongod + sidecar agent); the agent renders versioned automation config and drives backups and lifecycle changes. Implementation details: headless Service for pod discovery, per-member L4 load‑balancers for external clients, CSI topology support, and a manual StatefulSet volume‑resize workaround (patch + recreate). Multicluster uses central/member clusters, automatic DR shuffling, and experiments with split‑horizon with separate internal/external addresses, Envoy routing, and leader/worker StatefulSet variants.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:21Introductions
- 0:47MongoDB Deployment Models
- 2:15MongoDB Kubernetes
- 3:56MongoDB Operator Architecture
- 4:15Operations Manager Custom Resource
- 5:57Load Balancers
- 6:44Control and Data Plane Separation
- 8:25Storage and Networking
- 9:33Networking
- 11:30Multicluster
- 13:18Future challenges
- 16:00Thank you
- 16:32Questions
related talks
27mDIY DBaaS with Percona Kubernetes Operators
27mDatabase Infrastructure with Open Source Kubernetes Database Operators
35mOrchestrating Resilient Data: Harnessing the Strength of Kubernetes with Operators
41mDatabases on Kubernetes Using a Custom Operator: Day 1, Day 2, and Beyond
08mLightning Talk: Should You Run Your Database on Kubernetes
44mDatabases on Kubernetes: Why You Should Care!
33mKafka Operator: Managing and Operating Kafka Clusters in Kubernetes [A]
53mAutomating Stateful Applications with Kubernetes Operators