kubernetes/cluster/addons/metrics-server
Sean McGinnis be131457ef
Remove stale analytics links from docs
Many README files and other docs contained a link to a an appspot
tracking app that is no longer active. Following the links leads to an
error about Go 1.9 no longer being supported. Go 1.9 support was dropped
in appspot in 2019 and disabled June 2020.

This also resulted in a broken image link displaying when viewing these
files on GitHub. Since the app is no longer functioning, and since it
causes a potentially (but granted, minor) confusing error to display,
this just removes those links as I don't believe they are needed
anymore.

Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-11-18 07:04:48 -06:00
..
auth-delegator.yaml
auth-reader.yaml
metrics-apiservice.yaml Move test/e2e use to v1 APIs 2019-06-03 14:46:08 -04:00
metrics-server-deployment.yaml Update yaml files to use seccomp GA syntax 2020-08-13 08:45:36 +01:00
metrics-server-service.yaml
OWNERS Revert "Merge pull request #93160 from logicalhan/triage-instrumentation" 2020-07-24 18:09:07 +05:30
README.md Remove stale analytics links from docs 2020-11-18 07:04:48 -06:00
resource-reader.yaml Bump addon resizer to 1.8.9 version 2020-05-28 19:37:01 +02:00

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.