mirror of
https://github.com/kubernetes-sigs/descheduler.git
synced 2026-01-28 14:41:10 +01:00
Clarify resource percentage calculation in README
This commit is contained in:
@@ -167,8 +167,11 @@ in the hope that recreation of evicted pods will be scheduled on these underutil
|
|||||||
parameters of this strategy are configured under `nodeResourceUtilizationThresholds`.
|
parameters of this strategy are configured under `nodeResourceUtilizationThresholds`.
|
||||||
|
|
||||||
The under utilization of nodes is determined by a configurable threshold `thresholds`. The threshold
|
The under utilization of nodes is determined by a configurable threshold `thresholds`. The threshold
|
||||||
`thresholds` can be configured for cpu, memory, and number of pods in terms of percentage. If a node's
|
`thresholds` can be configured for cpu, memory, and number of pods in terms of percentage (the percentage is
|
||||||
usage is below threshold for all (cpu, memory, and number of pods), the node is considered underutilized.
|
calculated as the current resources requested on the node vs [total allocatable](https://kubernetes.io/docs/concepts/architecture/nodes/#capacity).
|
||||||
|
For pods, this means the number of pods on the node as a fraction of the pod capacity set for that node).
|
||||||
|
|
||||||
|
If a node's usage is below threshold for all (cpu, memory, and number of pods), the node is considered underutilized.
|
||||||
Currently, pods request resource requirements are considered for computing node resource utilization.
|
Currently, pods request resource requirements are considered for computing node resource utilization.
|
||||||
|
|
||||||
There is another configurable threshold, `targetThresholds`, that is used to compute those potential nodes
|
There is another configurable threshold, `targetThresholds`, that is used to compute those potential nodes
|
||||||
|
|||||||
Reference in New Issue
Block a user