Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add description about pod nanny #490

Merged
merged 1 commit into from
Jul 12, 2018
Merged

add description about pod nanny #490

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,14 @@ kube-state-metrics exposes its own metrics under `--telemetry-host` and `--telem

### Resource recommendation

Resource usage changes with the size of the cluster. As a general rule, you should allocate
Resource usage for kube-state-metrics changes with the Kubernetes objects(Pods/Nodes/Deployments/Secrects etc.) size of the cluster.
To some extent, the Kubernetes objects in a cluster are in direct proportion to the node number of the cluster.
[addon-resizer](https://github.com/kubernetes/autoscaler/tree/master/addon-resizer)
can watch and automatically vertically scale the dependent container up and down based on the number of nodes.
Thus kube-state-metrics uses `addon-resizer` to automatically scale its resource request. As for the detailed usage about
`addon-resizer` please go to its [ReadMe](https://github.com/kubernetes/autoscaler/tree/master/addon-resizer#nanny-program-and-arguments).

As a general rule, you should allocate

* 200MiB memory
* 0.1 cores
Expand Down