github/node-problem-detector
1
0
Fork 0
mirror of https://github.com/kubernetes/node-problem-detector.git synced 2026-08-19 04:06:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1037 from guettli/patch-2
CodeQL / Analyze (go) (push) Failing after 2m9s
Scorecard supply-chain security / Scorecard analysis (push) Failing after 1m18s

Browse Source 
Removed draino from README
This commit is contained in:
Kubernetes Prow Robot
2025-03-24 11:56:33 -07:00
committed by GitHub
parent f6bb4f7b55 d6cfed982a
commit 4022575bf9
1 changed files with 0 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
-10
View File
@@ -279,16 +279,6 @@ detected by the node-problem-detector. Remedy systems observe events and/or node
conditions emitted by the node-problem-detector and take action to return the
Kubernetes cluster to a healthy state. The following remedy systems exist:
* [**Draino**](https://github.com/planetlabs/draino) automatically drains Kubernetes
nodes based on labels and node conditions. Nodes that match _all_ of the supplied
labels and _any_ of the supplied node conditions will be prevented from accepting
new pods (aka 'cordoned') immediately, and
[drained](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/)
after a configurable time. Draino can be used in conjunction with the
[Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)
to automatically terminate drained nodes. Refer to
[this issue](https://github.com/kubernetes/node-problem-detector/issues/199)
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)