Closed Osshaikh closed 5 months ago
@Osshaikh could you please share a sample node yaml and pod yaml so it's easier to understand the problem?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
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:
What k8s version are you using (
kubectl version
)?kubectl version
OutputWhat 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
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