How Kubernetes CPU Manager Pins Cause Node Drain Failures

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How Kubernetes CPU Manager Pins Cause Node Drain Failures

Listen for free

View show details

Kubernetes CPU Manager static policy seems like a performance win, pinning pods to specific CPU cores. But when you need to drain a node for maintenance, those pinned pods refuse to move—or worse, they crash on restart. In this episode, Lucas and Luna dissect the tension between CPU pinning and node lifecycle. They walk through a real scenario where a 32-core production node stalled a rolling update for 45 minutes because kubelet couldn't evict a CPU Manager pod cleanly. They explain the CPU Manager's topology-aware allocation, the eviction logic gap, and the workarounds: using descheduler with a custom strategy, setting `cpuManagerPolicy: none` for drain-sensitive workloads, and tweaking kubelet eviction thresholds. If your cluster has latency-sensitive apps pinned to cores, this episode will save you from a messy node drain. #Kubernetes #CPUManager #NodeDrain #Kubelet #StaticPolicy #TopologyManager #DevOps #ClusterLifecycle #PodEviction #Descheduler #LatencySensitive #CloudNative #Infrastructure #SRE #Technology #FexingoBusiness #BusinessPodcast #DevOpsDaily Keep every episode free: buymeacoffee.com/fexingo

No reviews yet