DevOps Daily with Fexingo · 2026-07-08 · 9 min
In DevOps Daily Episode 99, Lucas and Luna dive into a dangerous and often overlooked Kubernetes behavior: cascading deletes of namespaces and the resource storms they trigger. Using a real incident at a mid-size SaaS company that accidentally deleted a production namespace, they explain how `kubectl delete namespace` doesn't just remove pods - it tears down every resource in that namespace in parallel, causing massive API server load, etcd latency spikes, and even cross-namespace side effects. They walk through the concrete failure cascade: from a namespace deletion to a 5-second etcd P99 latency increase, to a 3-minute control plane unavailability. They also cover mitigation strategies like using finalizers on critical namespaces, implementing namespace deletion prevention with admission webhooks, and setting up etcd request rate limiting. This episode gives DevOps engineers a specific, actionable understanding of a hazard rarely covered in training materials.
How Kubernetes ServiceAccount Token Expiration Breaks CI Workflows75 / 100How Kubernetes StatefulSet PVC Resizing Causes Node Disk Failures94 / 100How Kubernetes Topology Spread Constraints Create Scheduling Hotspots95 / 100How Kubernetes CRD Versioning Breaks Controller Upgrades90 / 100How Kubernetes Audit Logging Causes etcd Performance Degradation91 / 100