DevOps & CI/CD
Bug Report
Kubernetes Pods stuck Pending: Insufficient cpu, untolerated taints and node affinity
A routine rollout left 14 Pods Pending with Insufficient cpu while dashboards showed nodes at 30 percent CPU. The scheduler counts requests, not usage, and a new tainted node pool hid the free capacity. Here is how we read the FailedScheduling message and fixed it.