DevOps Daily with Fexingo · 2026-07-23 · 10 min
Episode 129 of DevOps Daily with Fexingo dives into a subtle but dangerous Kubernetes behavior: PodDisruptionBudget violations during voluntary evictions. Lucas and Luna walk through a real incident where a cluster running a critical payment service on 3 replicas with minAvailable=2 saw a complete outage during a node drain. The problem? The PDB only counts pods that are healthy according to readiness probes - but the operator assumed all 3 were eligible. When one pod had a stale ready state and another was being recreated, the eviction controller allowed the drain to proceed, dropping below the minimum. The hosts explain how PDBs interact with readiness gates, why 'voluntary disruption' is misleading, and a concrete fix: use maxUnavailable instead of minAvailable, and always combine with PodHealthyPolicy. No hot takes - just an operational war story that could save your next maintenance window.
How Kubernetes Namespace Quotas Trigger Unexpected Failures58 / 100Why Your Kubernetes Cost Reports Are Lying To YouHow Kubernetes Node Pools Can Cost You More Than You ThinkHow Kubernetes Pod Overhead Changes Node Capacity CalculationsHow Kubernetes Pod Security Admission Blocks Risky Workloads