Configuring and Deploying Stateful Applications with PetSet
summary
Kubernetes 1.3 adds PetSet / StatefulSet to give each replica a stable identity and its own persistent volume via volumeClaimTemplate, demonstrated by a three-member ZooKeeper cluster (zoo-0..2) that can read/write across members. The demo uses init containers to generate configs, and Kubernetes 1.5 adds graceful-deletion to avoid split-brain during node failures. StatefulSets work but initially forbid in-place updates; dynamic provisioning, fencing, stable IPs and better tooling are listed as future work.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:56What is a Stateful Set
- 3:33Stateless Replication
- 9:01Data Safety
- 9:32Three Laws of PetSet
- 11:14Demo
- 14:23What is PetSet
- 18:52DNS Schema
- 21:37PetSet IP Addresses
- 24:34Its Not Magic
- 27:48Graceful Deletion
- 31:20Fencing
- 34:11Local Persistent Storage
- 35:44No Template Expansion
- 37:51Documentation
- 39:16Example
- 41:41Distributed Systems
- 43:04Persistent Volumes
- 44:41Feedback Loop
related talks
25mStatefulsets on Kubernetes: The Guardians of Your Data Galaxy
29mStateful Workloads in Kubernetes: A Deep Dive
32mDon’t Hassle Me, I’m Stateful
37mStateful vs Stateless Container Patterns in Kubernetes, a Deeper Analysis
37mBuilding Stateful Workloads in Kubernetes
01h 19mTutorial: Back to Basics: Hands-On Deployment of Stateful Workloads on Kubernetes
20mDeployments vs StatefulSets vs Daemonsets
05mUpgrading Stateful Sets in Constrained Environment