Why Kubernetes Pods Restart When Nodes Reboot
from DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations Hosted by Fexingo
When a Kubernetes node reboots for a kernel update or hardware maintenance, pods don't just vanish and come back cleanly. The kubelet marks them as terminated, the container runtime loses state, and what looks like a routine maintenance window turns into failed readiness probes, stuck terminating pods, and a cascade of restarts. In episode 158 of DevOps Daily, Lucas and Luna break down the actual mechanics of node reboot behavior: how the kubelet handles graceful shutdown, why container runtimes like containerd and CRI-O can orphan processes, and why your deployment's restartPolicy is the hidden variable that decides whether that reboot is a blip or a production incident. They also walk through a real scenario where a node reboot during off-peak hours caused a payment service to restart with cold caches, triggering a 5x latency spike. If you've ever wondered why your pods don't come back the way they left, or why a simple reboot feels like playing roulette with your uptime, this episode gives you the mental model and the practical mitigations: preStop hooks, terminationGracePeriodSeconds, and podDisruptionBudgets that actually work. #Kubernetes #NodeReboot #Kubelet #ContainerRuntime #PodRestart #DevOps #SRE #CloudNative #Containerd #CRIO #PreStopHook #TerminationGracePeriod #PodDisruptionBudget #SiteReliability #Infrastructure #Tech #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.