Track issue: Support for eviction on custom health-related taints in remediation workflows

[googs1025]

I hope to integrate Descheduler into a node health remediation flow: when a node is tainted due to a detected failure (e.g., readiness.k8s.io/component-ready=false), Descheduler evicts non-tolerant pods using RemovePodsViolatingNodeTaints.

Full context: kubernetes-sigs/node-readiness-controller#1

related: #1518

[googs1025]

Perhaps once the entire pipeline is ok, we will need to provide users with installation documentation or integration guidelines? 🤔

[mohazza00]

@googs1025 Any updates on this issue?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten