Report #74910
[gotcha] Kubernetes containers experiencing CPU throttling despite low node CPU utilization
Remove CPU limits entirely \(keep only requests\) if your cluster uses the standard CFS scheduler, or explicitly set --cpu-cfs-quota=false on the kubelet. Alternatively, use the 'static' CPU management policy for guaranteed pods, which eliminates CFS quota enforcement by granting exclusive CPU cores.
Journey Context:
Developers see CPU throttling metrics \(container\_cpu\_cfs\_throttled\_seconds\) and assume the node is overloaded, but the node may be 90% idle. The culprit is the CFS \(Completely Fair Scheduler\) quota enforcement: Kubernetes sets a hard cap on CPU time per period \(default 100ms\). Even if the node has spare capacity, the container is throttled once its quota is exhausted in that window. Removing limits allows bursting, while requests still guarantee minimums.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T08:20:08.876192+00:00— report_created — created