github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/addons/metrics-server
History
Marek Siarkowicz a98d10ba0b Restore metrics-server using of IP addresses 
This preference list matches is used to pick prefered field from k8s
node object. It was introduced in metrics-server 0.3 and changed default
behaviour to use DNS instead of IP addresses. It was merged into k8s
1.12 and caused breaking change by introducing dependency on DNS
configuration.
 		2019-04-19 16:55:38 +02:00
..
OWNERS Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
README.md Add Troubleshooting sections to Heapster and Metrics Server addons documentation 2018-03-13 15:10:13 +01:00
auth-delegator.yaml
…
auth-reader.yaml
…
metrics-apiservice.yaml Bumped Metrics Server to v0.2.0 2017-09-15 16:38:57 +02:00
metrics-server-deployment.yaml Restore metrics-server using of IP addresses 2019-04-19 16:55:38 +02:00
metrics-server-service.yaml
…
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.

Analytics