Add note about CPU limits
This commit is contained in:
parent
50995f18d5
commit
fac66de438
|
|
@ -125,6 +125,8 @@ For clusters of more than 100 nodes, allocate at least
|
||||||
|
|
||||||
These numbers are based on [scalability tests](https://github.com/kubernetes/kube-state-metrics/issues/124#issuecomment-318394185) at 30 pods per node.
|
These numbers are based on [scalability tests](https://github.com/kubernetes/kube-state-metrics/issues/124#issuecomment-318394185) at 30 pods per node.
|
||||||
|
|
||||||
|
Note that if CPU limits are set too low, kube-state-metrics' internal queues will not be able to be worked off quickly enough, resulting in increased memory consumption as the queue length grows. If you experience problems resulting from high memory allocation, try increasing the CPU limits.
|
||||||
|
|
||||||
### kube-state-metrics vs. Heapster
|
### kube-state-metrics vs. Heapster
|
||||||
|
|
||||||
[Heapster](https://github.com/kubernetes/heapster) is a project which fetches
|
[Heapster](https://github.com/kubernetes/heapster) is a project which fetches
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue