Orchestrating Resilient Data: Harnessing the Strength of Kubernetes with Operators
summary
Deploys Couchbase into Kubernetes using a dedicated Operator (install operator + admission controller, CRD, then cluster YAML or Helm) and demonstrates a 3-node cluster sustaining 50,000 req/s from a pillowfight pod. The Operator implements level‑5 features: automated provisioning, backups, rolling upgrade, failover and rebalancing. Demo kills a node; operator recreates pod, claims PV, streams data from replicas and rebalances with no downtime. Block storage (PV/PVC/EBS) is recommended over NFS.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 1:12Kubernetes advantages and challenges
- 3:43Lowering operational costs with Kubernetes
- 5:52Kubernetes architecture for stateful apps
- 8:45Introduction to Couchbase
- 12:42Couchbase's cloud-native design
- 16:02Couchbase Operator features
- 19:37Operator deployment and benefits
- 23:16Live demo of failover handling
- 27:13Q&A session
related talks
44mDatabases on Kubernetes: Why You Should Care!
45mDatabases on Kubernetes: Why you should care
53mAutomating Stateful Applications with Kubernetes Operators
41mDatabases on Kubernetes Using a Custom Operator: Day 1, Day 2, and Beyond
21mStory of a Kubernetes Go Operator
25mLessons Learned from Building a Database Operator
37mBuilding a Storage Cluster with Kubernetes
45mBuild Your Kubernetes Operator with the Right Tool!