City platform engineers aggregate kubectl top pod views and notice one namespace dominating cluster CPU. What capability does that analysis demonstrate?
Select an answer to reveal the explanation.
Short Explanation
Zoom out from one pod and the hotspot jumps out—one namespace eating the pie. Aggregation turns raw top output into 'who is burning the cluster.'
Full Explanation
Aggregating pod metrics by namespace (or labels) lets administrators attribute cluster CPU or memory load to particular teams or apps. That attribution guides quotas, limits, and remediation. It is unrelated to Ingress controller binding, etcd encryption, or NetworkPolicy deletion.