kubernetes/cluster/addons/metrics-server
shuaichen 3d620192d9 Use 10250 as targetPort for metrics-server
Metrics-server's usage of privileged port 443 as targetPort requires
elevated permissions than necessary and violates principle of least
privilege.
2021-10-28 03:10:15 +00: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 Use 10250 as targetPort for metrics-server 2021-10-28 03:10:15 +00: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 Give metrics server permission to read node stats. 2021-10-27 13:32:42 +00: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.