DevOps Daily with Fexingo · 2026-08-29 · 10 min
In this episode of DevOps Daily, Lucas and Luna dig into Kubernetes pod overhead - the CPU and memory each pod consumes before your container even starts. They walk through a real scenario where a cluster's node capacity looked fine on paper but ran out of resources during a rolling deployment. Lucas explains how the kubelet accounts for pod overhead, why the kubelet's eviction signals can trigger early, and how to set resource requests so you don't overcommit. They also touch on the trade-off between bin-packing efficiency and predictability, and share a quick tool they use to model capacity before a rollout. If you've ever been surprised by a node that's 'full' even though your requests look small, this episode gives you a concrete mental model and a few practical checks. Tune in for a focused, jargon-light conversation that leaves you with one usable insight. #Kubernetes #PodOverhead #NodeCapacity #DevOps #CloudNative #SRE #ContainerOrchestration #ResourceManagement #Kubelet #ClusterOperations #TechPodcast #FexingoBusiness #BusinessPodcast #SoftwareEngineering #InfrastructureAsCode #CapacityPlanning #Monitoring #K8sTips 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 Security Admission Blocks Risky WorkloadsHow Kubernetes Service Meshes Hide Network Latency