DevOps Daily with Fexingo · 2026-08-11 · 9 min
In this episode of DevOps Daily, Lucas and Luna dig into Kubernetes Pod Disruption Budgets and why they are a common culprit behind node drain stalls. They walk through a real-world scenario where a PDB with minAvailable set too high prevented a node from being drained, causing a cascade of failed evictions and stuck deployments. The conversation covers the difference between minAvailable and maxUnavailable, how PDBs interact with voluntary disruptions and node drains, and practical tuning strategies to avoid over-constraining your cluster. They also discuss monitoring PDB status and using tools like Descheduler and PDB Radar to prevent stalls. If you've ever watched a node drain hang indefinitely, this episode gives you the mental model and the concrete fixes you need. Tune in for a focused, jargon-free breakdown of a classic Kubernetes failure mode. #Kubernetes #PodDisruptionBudgets #NodeDrain #DevOps #CI #CD #SRE #CloudNative #ContainerOrchestration #ClusterOperations #TechOps #InfrastructureAsCode #FexingoBusiness #BusinessPodcast #TechnologyPodcast #DevOpsDaily #K8s #KubernetesTroubleshooting Keep every episode free: buymeacoffee.com/fexingo
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