kubernetes/cluster/addons/cluster-monitoring
Kubernetes Submit Queue ca62aa1ee2
Merge pull request #62756 from wangzhen127/seccomp-in-addon
Automatic merge from submit-queue. 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>.

Use default seccomp profile for unprivileged addons

**What this PR does / why we need it**:
This PR sets the default seccomp profile of unprivileged addons to 'docker/default'. This PR is a followup of [#62662](https://github.com/kubernetes/kubernetes/pull/62662) and [#62671](https://github.com/kubernetes/kubernetes/pull/62671). We are using 'docker/default' instead of 'runtime/default' in addons in order to handle node version skew. When seccomp profile is applied automatically by default later, we can remove those annotations.

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #39845

**Special notes for your reviewer**:

**Release note**:

```release-note
NONE
```
2018-05-23 17:29:16 -07:00
..
google Merge pull request #62756 from wangzhen127/seccomp-in-addon 2018-05-23 17:29:16 -07:00
googleinfluxdb Merge pull request #62756 from wangzhen127/seccomp-in-addon 2018-05-23 17:29:16 -07:00
influxdb Merge pull request #62756 from wangzhen127/seccomp-in-addon 2018-05-23 17:29:16 -07:00
stackdriver Merge pull request #62756 from wangzhen127/seccomp-in-addon 2018-05-23 17:29:16 -07:00
standalone Merge pull request #62756 from wangzhen127/seccomp-in-addon 2018-05-23 17:29:16 -07:00
heapster-rbac.yaml update to rbac v1 in yaml file 2017-08-21 17:29:37 +08: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

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