Databases on Kubernetes: Why you should care
summary
Claims Kubernetes is production-ready for databases because StatefulSets + CRDs + production images let operators automate real operations. The page shows a Couchbase operator demo that deploys a 3-node cluster, wires a Spring Boot app, deletes a node and the operator rejoins and rebalances data, then scales 3→4 nodes with no manual intervention. It notes storage tradeoffs (ephemeral vs remote vs local PVs GA), out-of-the-box backups/replication to S3, and up to 10% perf hit on some workloads.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 2:02Stateless containers
- 2:28Database in containers
- 3:03What have changed
- 3:15Whats important
- 4:57Problems with databases
- 5:35Configuration management tools
- 6:15Absolute certainty features
- 8:45Database configuration
- 9:09Operator framework
- 10:25Automation
- 11:27Database as a Service
- 12:03Real Example
- 13:05Operators
- 14:05Creating a culturebased cluster
- 14:55Creating a spring boot
- 16:50Selfhealing mechanism
- 17:53Control delete
- 18:47State applications
- 20:03Database scaling
- 20:45Database recovery
- 22:06Database security
- 22:55Data nodes
- 24:01Apply configuration
- 25:10Automated backups
- 26:07Managing the database
- 26:49Database operators
- 28:02When should I run my database
- 32:24What is an operator
- 33:22Storage
- 34:58Local Persistent Storage
- 37:24Performance
- 38:50Benchmarks
- 39:31Migration
- 40:09Operator Hub
- 40:47Stateful Containers
- 41:58Questions
related talks
44mDatabases on Kubernetes: Why You Should Care!
26mChallenges of Managing Stateful Applications in Kubernetes
35mStateful Apps On Kubernetes - Bring Them On!
45mBest Practices for Running Databases on Kubernetes
08mLightning Talk: Should You Run Your Database on Kubernetes
47mFrom a Database in Container to DBaaS on Kubernetes
25mStatefulsets on Kubernetes: The Guardians of Your Data Galaxy
35mHow to put a Database in Kubernetes