RemovePodsViolatingNodeTaints Profile/strategies doesnt work

[Osshaikh]

What version of descheduler are you using?

descheduler version: 0.27

Does this issue reproduce with the latest release? Yes

Which descheduler CLI options are you using? not uisng CLI explicitly , Deployed Descheuler as Deployment Sets

Please provide a copy of your descheduler policy config file apiVersion: "descheduler/v1alpha2" kind: "DeschedulerPolicy" profiles:

• name: ProfileName pluginConfig:
  • name: "RemovePodsViolatingNodeTaints" args: namespaces: exclude:
    • "kube-system" plugins: deschedule: enabled:
    • "RemovePodsViolatingNodeTaints"

What k8s version are you using (kubectl version)?

kubectl version Output

$ kubectl version
1.24.9

What did you do? I have thre node AKS cluster (Azure Cloud), with taints on nodes in my app deployment i have exact toleration for one of node taints If turnoff one of my node, then pods get schedule to any available node. After starting node again , ideally descheudler should check for pods violating node taints and evict those pods running on different nodes but i dont see that happenning descheduler doesnt evictds pods based on node taints violation at all, I have tried using additonal configuration options to match toleration/taints details that also doesnt seem to take effect

• "RemovePodsViolatingNodeTaints" configuration: podFilters:
  • type: "Taints" taints:
    • operator: "Equals" key: "kubernetes.azure.com/scalesetpriority" value: "spot" effect: "NoSchedule"
    • operator: "DoesNotExist" key: "kubernetes.azure.com/scalesetpriority"

      You could reproduced the same steps by taints node on your cluster and then having your deployments with tolerations matching one of node taints Then you should turnoff nodes that has same taints as your deployment so that pods can be schedule other nodes turn on your nodes again for descheduler to check pods violating node taints and evict those pods so that they could run on thier originall tainted node

What did you expect to see? Deschedule evicting pods which are violating node taints and running on different node rather than node taint match by thier tolerations

What did you see instead? I see that descheduler doesnt do pods evictions at all atleast for nodeviolation strategy

[damemi]

@Osshaikh could you please share a sample node yaml and pod yaml so it's easier to understand the problem?

[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

[k8s-triage-robot]

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

This bot triages 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:

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/descheduler/issues/1182#issuecomment-2016621593): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.