History

Mike Danese 8bcb178da3 explicitly set run as user/group in addons that set this config in their dockerfile		2018-11-16 19:32:44 +00:00
..
google	explicitly set run as user/group in addons that set this config in their dockerfile	2018-11-16 19:32:44 +00:00
googleinfluxdb	explicitly set run as user/group in addons that set this config in their dockerfile	2018-11-16 19:32:44 +00:00
influxdb	explicitly set run as user/group in addons that set this config in their dockerfile	2018-11-16 19:32:44 +00:00
stackdriver	explicitly set run as user/group in addons that set this config in their dockerfile	2018-11-16 19:32:44 +00:00
standalone	explicitly set run as user/group in addons that set this config in their dockerfile	2018-11-16 19:32:44 +00: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.