github/node-problem-detector
1
0
Fork 0
mirror of https://github.com/kubernetes/node-problem-detector.git synced 2026-08-28 01:47:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #419 from KohlsTechnology/remedy-system-docs

Browse Source 
Document Using Descheudler As a Remedy System
This commit is contained in:
Kubernetes Prow Robot
2020-03-10 14:01:36 -07:00
committed by GitHub
parent ab5ea72c74 f603f26afa
commit c709314cd7
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4
View File
@@ -248,6 +248,10 @@ Kubernetes cluster to a healthy state. The following remedy systems exist:
to automatically terminate drained nodes. Refer to to automatically terminate drained nodes. Refer to
[this issue](https://github.com/kubernetes/node-problem-detector/issues/199) [this issue](https://github.com/kubernetes/node-problem-detector/issues/199)
for an example production use case for Draino. for an example production use case for Draino.
* [**Descheduler**](https://github.com/kubernetes-sigs/descheduler) strategy RemovePodsViolatingNodeTaints
evicts pods violating NoSchedule taints on nodes. The k8s scheduler's TaintNodesByCondition feature must
be enabled. The [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)
can be used to automatically terminate drained nodes.
# Testing # Testing