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
Marek Siarkowicz 9e9b906047 Update gcp images with security patches 
[stackdriver addon] Bump prometheus-to-sd to v0.5.0 to pick up security fixes.
[fluentd-gcp addon] Bump fluentd-gcp-scaler to v0.5.1 to pick up security fixes.
[fluentd-gcp addon] Bump event-exporter to v0.2.4 to pick up security fixes.
[fluentd-gcp addon] Bump prometheus-to-sd to v0.5.0 to pick up security fixes.
[metatada-proxy addon] Bump prometheus-to-sd v0.5.0 to pick up security fixes.
 		2019-03-15 09:24:32 +01:00
..
google delete all duplicate empty blanks 2019-02-23 10:28:04 +08:00
googleinfluxdb Change add-on manifests to apps/v1 2018-12-19 17:30:59 -05:00
influxdb delete all duplicate empty blanks 2019-02-23 10:28:04 +08:00
stackdriver Update gcp images with security patches 2019-03-15 09:24:32 +01:00
standalone delete all duplicate empty blanks 2019-02-23 10:28:04 +08: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
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