Upgrading Stateful Sets in Constrained Environment
summary
Upgrade of stateful sets succeeds on fixed bare-metal appliances with no shared storage and no extra capacity, running on 20 CPU 128GB boxes and servicing ~1,000,000 requests/sec. Uses PersistentVolume local storage class so PVs bind to the same node as pods, combines sharding and replicas for state distribution (examples: Cassandra and Elasticsearch), and relies on kube-proxy internal load balancing to route traffic to the active node. Rolling upgrades complete without added resources.
AI-written summary · about
related talks
32mDon’t Hassle Me, I’m Stateful
32mMulti-Cluster Stateful Set Migration: A Solution To Upgrade Pain
46mConfiguring and Deploying Stateful Applications with PetSet
35mWhen StatefulSets are not enough
25mStatefulsets on Kubernetes: The Guardians of Your Data Galaxy
22mRunning distributed stateful system on Kubernetes - Beyond Statefulsets
32mContaining an Elephant
42mImproving Availability for Stateful Applications in Kubernetes