kubernetes-sigs/metrics-server

Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 9th, 2026
Created on May 23rd, 2017
Open Issues & Pull Requests: 55 (+0)
GitHub issues: Enabled
Number of forks: 2,040
Total Stargazers: 6,716 (+0)
Total Subscribers: 89 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 19.1 days
90th percentile: 71.0 days
Tracked items: 120

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 76% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/bug" is answered fastest, typically in about 26 hours, while "kind/feature" waits about 8 days. Only 2% of issues opened in the past year have been closed. Three people close 60% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 29
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 589 days
Stale 30+ days: 23
Stale 90+ days: 7

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 4
Events in 7 days: 14

Top labels

  • needs-triage (77)
  • lifecycle/rotten (39)
  • triage/accepted (33)
  • kind/support (31)
  • kind/bug (28)
  • kind/feature (27)
  • help wanted (8)
  • helm-chart (6)

Detailed Description

Metrics Server is a Kubernetes component that collects container resource metrics from Kubelets and exposes them through the Metrics API for use by autoscaling systems.

The tool solves the problem of providing real-time resource utilization data to Kubernetes autoscaling pipelines. It collects CPU and memory metrics from Kubelets every 15 seconds and exposes them via the Metrics API, which is consumed by Horizontal Pod Autoscaler and Vertical Pod Autoscaler. The metrics are also accessible through kubectl top for debugging autoscaling behavior. The project emphasizes that it is designed specifically for autoscaling purposes and should not be used as a general monitoring solution or to forward metrics to external monitoring systems.

Metrics Server is appropriate for clusters that need CPU and memory-based horizontal autoscaling or resource recommendations from the Vertical Pod Autoscaler. It works on most Kubernetes distributions but requires specific cluster configuration: the kube-apiserver aggregation layer must be enabled, nodes must have Webhook authentication and authorization, Kubelet certificates must be signed by the cluster Certificate Authority (or certificate validation can be disabled), and the container runtime must support container metrics RPCs or cAdvisor. Network connectivity must be established between the control plane and Metrics Server, and between Metrics Server and all node Kubelets. For use cases requiring accurate historical metrics, non-CPU/memory-based autoscaling, or monitoring of non-Kubernetes systems, the README recommends full monitoring solutions like Prometheus instead.

The project maintains a single deployment model designed for broad cluster compatibility, with resource efficiency tuned to use minimal CPU and memory overhead per node and support for clusters up to 5,000 nodes. Development activity shows consistent engagement with the codebase through regular updates and maintenance of the core metrics collection and exposure functionality.