Metrics Server
A cluster add-on that collects current CPU and memory use from every kubelet so kubectl top and the autoscaler can read it.
In more detail
It keeps only recent values in memory, so it is not a monitoring system with history. Without it, kubectl top fails and a HorizontalPodAutoscaler that scales on CPU cannot act. kind does not install it by default.
Example
kubectl top pod webRelated terms
- HorizontalPodAutoscaler — The Kubernetes object that raises or lowers a workload's replica count automatically to keep a metric, such as CPU use, near a target.
- kubelet — The agent on every Kubernetes node that starts and watches the node's containers and reports back to the API server.
Taught in
- Usage, Requests And The Pod That Will Not Fit — Certified Kubernetes Administrator (CKA) Exam Prep
- Helm And Kustomize For Cluster Components — Certified Kubernetes Administrator (CKA) Exam Prep
- Self-Healing And Autoscaling: Who Restarts, Who Replaces, Who Adds — Certified Kubernetes Administrator (CKA) Exam Prep
- Monitoring With The Built-in CLI — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Observability: Timed Drill And Checkpoint — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Requests, Limits And Quotas — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Requests, Limits, Quotas And Horizontal Autoscaling — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: OOMKilled, Throttling And Evictions — Kubernetes: Production-Grade Container Orchestration