Stateful Apps On Kubernetes - Bring Them On!
summary
Enterprise teams run databases in Kubernetes as first-class apps, deployable by developers with CI/CD, operators and CSI drivers, and they report surprising scale: 3,000 nodes, 65 clusters, 70,000 containers and about 1,500 statefulsets supporting ~550 database clusters. Tools called out: CSI, PV/PVC, affinity rules, database replication (native or storage-level), Kafka and IBM MQ. Persistent storage still needs backups, hiring Kubernetes+DB talent is the bottleneck, and one migration reports 72 cores saved by changing deployment patterns.
AI-written summary · about
chapters (12)
- 0:00Stateful apps on Kubernetes
- 2:27Cloud-native journeys
- 7:00Stateful workloads
- 10:30Containers as packaging
- 13:18Stateful apps lifecycle
- 16:46Kubernetes talent training
- 19:32Data lifecycle upgrades
- 24:03Where Kubernetes went right and wrong
- 27:55Future of stateful apps
- 31:52Geo-distributed stateful apps
- 33:57Support models tooling
- 35:00Closing remarks Q&A
related talks
26mChallenges of Managing Stateful Applications in Kubernetes
45mDatabases on Kubernetes: Why you should care
25mStatefulsets on Kubernetes: The Guardians of Your Data Galaxy
25mPostgres on Kubernetes for the Reluctant DBA
59mA DevOps State of Mind: Managing Microservices + Databases with Kubernetes
45mFrom Laptop to Cloud: Developing Cloud Native Applications with Containerized Databases
47mFrom a Database in Container to DBaaS on Kubernetes
08mLightning Talk: Should You Run Your Database on Kubernetes