A school-district worker node reports high CPU while kubectl top pods shows only modest application usage. What should the administrator investigate next?
Select an answer to reveal the explanation.
Short Explanation
Pod top can look calm while the node is screaming—kubelet, container runtime, and other system daemons still burn CPU. Peel the onion: look at the node itself, not only the app pods.
Full Explanation
Node-level CPU includes kubelet, the container runtime, OS services, and other non-pod processes in addition to scheduled pods. Modest pod metrics therefore do not rule out node pressure from system components. Administrators should inspect host/process metrics and kubelet health rather than resizing every workload or removing control-plane addons blindly.