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

Merge pull request #971 from sanposhiho/patch-1

Browse Source 
doc: fix a markdown's style on user-guide
This commit is contained in:
Kubernetes Prow Robot
2022-10-06 07:09:52 -07:00
committed by GitHub
parent 7c7e1b9cdc 4fb781ae7c
commit bed8693c69
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/user-guide.md
View File

@@ -159,6 +159,7 @@ strategies:
``` ```
### 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
[Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler) to automatically remove [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler) to automatically remove
@@ -167,6 +168,7 @@ There is a feature called TaintNodeByCondition of the node controller that takes
The Descheduler will then deschedule workloads from those Nodes. Finally, if the descheduled Node's resource The Descheduler will then deschedule workloads from those Nodes. Finally, if the descheduled Node's resource
allocation falls below the Cluster Autoscaler's scale down threshold, the Node will become a scale down candidate allocation falls below the Cluster Autoscaler's scale down threshold, the Node will become a scale down candidate
and can be removed by Cluster Autoscaler. These three components form an autohealing cycle for Node problems. and can be removed by Cluster Autoscaler. These three components form an autohealing cycle for Node problems.
--- ---
**NOTE** **NOTE**