Multi-Cluster Stateful Set Migration: A Solution To Upgrade Pain
summary
Shows a concrete method to move an M3DB-backed StatefulSet between GKE clusters using multi-cluster services for discovery, a Kubernetes enhancement like StatefulSet Partition / CAP-335 to split replica ordinals, and explicit migration of PV/PVC and configmap dependencies. Demo preserves client-side quorum (two-of-three), uses pod readiness gates and cross-cluster PDB coordination to avoid data loss, and relies on graceful termination and attach/detach checks so replicas follow storage while DNS and operator reconciliation complete.
AI-written summary · about
chapters (9)
- 0:00Start
- 7:22Migration Challenges: Overview
- 8:33Migration Challenges: Network
- 10:24Migration Challenges: Storage
- 11:53Migration Challenges: Orchestration
- 14:25Building Blocks: Multi-Cluster Services
- 15:51Building Blocks: KEP-3335
- 17:03Building Blocks: Tying Pieces Together
- 21:54What's Next?
related talks
32mDon’t Hassle Me, I’m Stateful
35mWhen StatefulSets are not enough
23mDancing With the Pods: Live Migration of a Database Fleet While Serving Millions of Queries
05mUpgrading Stateful Sets in Constrained Environment
38mMulticluster Kubernetes, today and tomorrow
46mConfiguring and Deploying Stateful Applications with PetSet
25mStatefulsets on Kubernetes: The Guardians of Your Data Galaxy
22mRunning distributed stateful system on Kubernetes - Beyond Statefulsets