Karpenter consolidation fixes idle EKS nodes

An analysis of ten months of operational logs from a custom Kubernetes node reaper tool revealed that most empty and idle nodes were caused by KEDA-scaled batch workloads and restrictive Karpenter consolidation budgets. The author explains how reconfiguring Karpenter's empty-node budgets and enabling node repair features resolved the issue, allowing the custom tool to serve primarily as a lightweight safety net. Open article →