github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/addons/cluster-monitoring
History
Kubernetes Submit Queue 62dc3ba8a0
Merge pull request #61396 from kawych/bump_heapster 
Automatic merge from submit-queue (batch tested with PRs 61396, 61321, 61443, 60911, 61461). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Bump Heapster to v1.5.2

**What this PR does / why we need it**:
Bump Heapster to v1.5.2

**Release note**:
```release-note
Bump Heapster to v1.5.2
```
 		2018-03-22 03:37:09 -07:00
..
google Bump Heapster to v1.5.2 2018-03-19 12:54:58 +01:00
googleinfluxdb Bump Heapster to v1.5.2 2018-03-19 12:54:58 +01:00
influxdb Bump Heapster to v1.5.2 2018-03-19 12:54:58 +01:00
stackdriver Bump Heapster to v1.5.2 2018-03-19 12:54:58 +01:00
standalone Bump Heapster to v1.5.2 2018-03-19 12:54:58 +01:00
OWNERS Add kawych to cluster-monitoring deployment owners 2017-11-17 13:48:20 +01:00
README.md Add Troubleshooting sections to Heapster and Metrics Server addons documentation 2018-03-13 15:10:13 +01:00
heapster-rbac.yaml update to rbac v1 in yaml file 2017-08-21 17:29:37 +08:00

README.md

Kubernetes Monitoring

Heapster enables monitoring and performance analysis in Kubernetes Clusters. Heapster collects signals from kubelets and the api server, processes them, and exports them via REST APIs or to a configurable timeseries storage backend.

More details can be found in Monitoring user guide.

Troubleshooting

Heapster supports up to 30 pods per cluster node. In clusters where there are more running pods, Heapster may be throttled or fail with OOM error. Starting with Kubernetes 1.9.2, Heapster 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):

  • Metrics not being exported
  • Horizontal Pod Autoscaler not working
  • kubectl top not working

Overwritten configuration persists through cluster updates, therefore may cause all effects above after a cluster update.

Analytics