Files

Damien Grisonnet 08a324bf51 cluster/addons: set metrics-resolution to 15s

Align metrics-server metrics-resolution with the upstream manifests so
that scalability tests are running a similar configuration of
metrics-server as the one we are running in the e2e tests.

Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>

2023-04-05 20:07:04 +02: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

cluster/addons: set metrics-resolution to 15s

2023-04-05 20:07:04 +02:00

metrics-server-service.yaml

…

OWNERS

Cleanup OWNERS files (No Activity in the last year)

2021-12-15 10:34:02 -05:00

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

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.