Databases on Kubernetes: Why You Should Care!
summary
Live demo shows a Couchbase Operator creating a Couchbase Enterprise 6.0 cluster from a CRD and StatefulSet, a cron job writing documents, then deleting a pod to simulate failure. Kubernetes restarts the pod, the operator calls the Couchbase API to join and rebalance shards, preserving data with 3 replicas and automatic rebalancing. Operator-driven upgrades support rollback; scaling from 3→4 nodes triggers another rebalance. Benchmarks show <1% difference on read-heavy workloads and up to 10% penalty on write-heavy small-range workloads; local persistent volumes are GA since k8s 1.14.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:39Fast forward to 2019..
- 2:04What have changed?
- 8:53Databases are stateful
- 9:07OPERATOR FRAMEWORK
- 12:20Provide a cloud agnostic Database-as-a-Service solution
related talks
45mDatabases on Kubernetes: Why you should care
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
26mChallenges of Managing Stateful Applications in Kubernetes
34mDatabases on Kubernetes
25mLessons Learned from Building a Database Operator
27mDatabase Infrastructure with Open Source Kubernetes Database Operators