DevOps Daily with Fexingo · 2026-07-19 · 11 min
In this episode of DevOps Daily with Fexingo, Lucas and Luna dive into a subtle but severe Kubernetes anti-pattern: PriorityClass starvation at the node level. They break down a real-world case where a team set a critical batch job's priority too high, causing it to preempt essential daemonsets and system pods, leading to node instability and failed scheduling. Lucas explains how the Kubernetes scheduler's preemption logic interacts with kubelet's resource allocation, why setting priorities without understanding the full hierarchy can backfire, and the three metrics you should monitor - preemption counts, pod eviction rates, and node pressure conditions - to catch starvation before it takes down your cluster. Luna pushes on whether kubectl describe node gives enough information, and they walk through a practical audit using PriorityClass objects and pod spec priority fields. If you've ever wondered why nodes look healthy but pods won't land, this episode gives you the debugging framework. No fluff, just the edge cases that break production.
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