History

Solly Ross 13d59fde9e Bump metrics-server to v0.3.1 This fixes an issue with overly aggressive discardings of node data sets when a single pod is missing data.		2018-09-17 11:34:29 -04: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	Bumped Metrics Server to v0.2.0	2017-09-15 16:38:57 +02:00
metrics-server-deployment.yaml	Bump metrics-server to v0.3.1	2018-09-17 11:34:29 -04:00
metrics-server-service.yaml	Made metrics-server critical service managed by addon-manager	2017-09-03 22:14:57 +02:00
OWNERS	Add kawych to Metrics Server owners	2018-01-11 16:36:38 +01:00
README.md	Add Troubleshooting sections to Heapster and Metrics Server addons documentation	2018-03-13 15:10:13 +01:00
resource-reader.yaml	Autoscaler metrics-server with pod-nanny	2017-10-06 14:40:55 +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.