Skip to content
Captain's Academy0
← Kubernetes sea chart
Island 3 · Logging & Monitoring · Port 3.1

Metrics server & kubectl top

Ask the Captain
Instagram
Which pod is eating your CPU?
You'll learn to

read node/pod usage and say where metrics come from (cAdvisor → kubelet)

Recap

  1. 1kubelet (cAdvisor) measures
  2. 2metrics-server collects, no history
  3. 3kubectl top reads (250m = ¼ core)
Check yourself

kubectl top says Metrics API not available. What's missing?

3.1

Stamp this lesson

Watched it and passed the check? Mark it in your logbook.