History

Kubernetes Prow Robot 082883cba3 Merge pull request #83362 from wawa0210/zx-metrics Bind metrics-server containers to linux nodes to avoid Windows scheduling on kubernetes cluster includes linux nodes and windows nodes		2019-12-09 03:10:02 -08:00
..
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	Merge pull request #83362 from wawa0210/zx-metrics	2019-12-09 03:10:02 -08:00
metrics-server-service.yaml	Made metrics-server critical service managed by addon-manager	2017-09-03 22:14:57 +02:00
OWNERS	Introduce sig-instrumentation aliases in OWNERS_ALISES and simplify OWNERS files	2019-10-10 14:04:20 +02:00
README.md	Fix link for resource metrics pipeline	2019-04-24 22:38:48 -06:00
resource-reader.yaml	fix metrics-server rbac	2019-10-02 16:44:26 +02:00

README.md

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.