kubernetes/cluster/addons/metrics-server
Humble Devassy Chirammal 4964f699db metrics-server: update to v0.8.1 and fix stale RBAC resourceName
Update metrics-server addon from v0.8.0 to v0.8.1.

Also fix the ClusterRole resource-reader which still referenced the
deployment name from v0.7.1 (metrics-server-v0.7.1). The addon-resizer
nanny needs get/patch permission on the current deployment name to
function correctly; without this fix the nanny requests would be
denied by RBAC.

Additionally update the README link from the archived
kubernetes-incubator org to the current kubernetes-sigs org.

Signed-off-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
2026-04-02 20:29:25 +05:30
..
auth-delegator.yaml Made metrics-server critical service managed by addon-manager 2017-09-03 22:14:57 +02:00
auth-reader.yaml Made metrics-server critical service managed by addon-manager 2017-09-03 22:14:57 +02:00
metrics-apiservice.yaml Move test/e2e use to v1 APIs 2019-06-03 14:46:08 -04:00
metrics-server-deployment.yaml metrics-server: update to v0.8.1 and fix stale RBAC resourceName 2026-04-02 20:29:25 +05:30
metrics-server-service.yaml Made metrics-server critical service managed by addon-manager 2017-09-03 22:14:57 +02:00
OWNERS Cleanup OWNERS files (No Activity in the last year) 2021-12-15 10:34:02 -05:00
README.md metrics-server: update to v0.8.1 and fix stale RBAC resourceName 2026-04-02 20:29:25 +05:30
resource-reader.yaml metrics-server: update to v0.8.1 and fix stale RBAC resourceName 2026-04-02 20:29:25 +05:30

Metrics Server

Metrics Server exposes core Kubernetes metrics via metrics API.

More details can be found in Core metrics pipeline documentation.

Troubleshooting

Metrics Server supports up to 30 pods per cluster node. In clusters where there are more running pods, Metrics Server may be throttled or fail with OOM error. Starting with Kubernetes 1.9.2, Metrics Server resource requirements may be overwritten manually. Learn more about Addon Resizer configuration

Important notices

Decreasing resource requirements for cluster addons may cause system instability. The effects may include (but are not limited to):

  • Horizontal Pod Autoscaler not working
  • kubectl top not working (starting with Kubernetes 1.10)

Overwritten configuration persists through cluster updates, therefore may cause all effects above after a cluster update.