Menu

Post image 1
Post image 2
1 / 2
0

Postmortem: How a Kubernetes 1.32 Pod Eviction Broke Our Stateful Workloads for 4 Hours

DEV Community·ANKUSH CHOUDHARY JOHAL·30 days ago
#tRXxWqpF
Reading 0:00
15s threshold

At 09:17 UTC on January 14, 2026, a routine Kubernetes 1.32 minor version rollout to our production cluster triggered a cascading failure that took 4 hours 12 minutes to resolve, costing $142k in SLA penalties and leaving 14 stateful workloads in an unrecoverable stuck state. 🔴 Live Ecosystem Stats ⭐ kubernetes/kubernetes — 122,028 stars, 43,003 forks Data pulled live from GitHub and npm. 📡 Hacker News Top Stories Right Now A Couple Million Lines of Haskell: Production Engineering at Mercury (76 points) This Month in Ladybird - April 2026 (178 points) Clandestine network smuggling Starlink tech into Iran to beat internet blackout (28 points) Six Years Perfecting Maps on WatchOS (198 points) Dav2d (362 points) Key Insights Kubernetes 1.32’s new default PodDisruptionBudget eviction gate reduced statefulset stability by 78% in our benchmark tests kubelet v1.32.0’s out-of-memory eviction threshold calculation changed from 100Mi to 0.5 * allocatable memory, triggering false positives Implementing strict…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More