Sok3t/descheduler
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/descheduler.git synced 2026-01-28 06:29:29 +01:00
Code Packages Releases Activity

add use case for lowNodeUtilization

Browse Source
This commit is contained in:
lixiang
2020-09-24 17:51:08 +08:00
parent 6042d717e9
commit 00f79aa28d
2 changed files with 35 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/user-guide.md
View File

@@ -75,6 +75,29 @@ strategies:
maxPodLifeTimeSeconds: 604800 # pods run for a maximum of 7 days maxPodLifeTimeSeconds: 604800 # pods run for a maximum of 7 days
``` ```
### Balance Cluster By Node Memory Utilization
If your cluster has been running for a long period of time, you may find that the resource utilization is not very
balanced. The `LowNodeUtilization` strategy can be used to rebalance your cluster based on `cpu`, `memory`
or `number of pods`.
Using the following policy configuration file, descheduler will rebalance the cluster based on memory by evicting pods
from nodes with memory utilization over 70% to nodes with memory utilization below 20%.
```
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
"LowNodeUtilization":
enabled: true
params:
nodeResourceUtilizationThresholds:
thresholds:
"memory": 20
targetThresholds:
"memory": 70
```
### Autoheal Node Problems ### Autoheal Node Problems
Descheduler's `RemovePodsViolatingNodeTaints` strategy can be combined with Descheduler's `RemovePodsViolatingNodeTaints` strategy can be combined with
[Node Problem Detector](https://github.com/kubernetes/node-problem-detector/) and [Node Problem Detector](https://github.com/kubernetes/node-problem-detector/) and

12
examples/low-node-utilization.yml Normal file
View File

@@ -0,0 +1,12 @@
---
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
"LowNodeUtilization":
enabled: true
params:
nodeResourceUtilizationThresholds:
thresholds:
"memory": 20
targetThresholds:
"memory": 70