JaneLiuL

if all nodes are underutilized, sort the nodes by utilization and evict pods on the least-utilized nodes. very good idea~~ could i have a try on this enhancement?

it seems we need to has some big picture potential to improve the descheduler for this part.

@dineshbhor sorry for i forget this issue, you can take this :)

/hold

i plan to use watcher as below before, but it seems too complicate on e2e , so just adjust the timeout on `TestTopologySpreadConstraint`, and also not return if pod still...

/hold cancel

hi @sudmis in your case, you have pod with more than one container, and you would like configure the descheduler to evict pod if one of the container phase is...

thanks @sudmis could you get the pod and show me the yaml? the pod READY is 2/3 right? `kubectl get pod xxx -o yaml` now for descheduler we do check...

thanks. i check your log, the pod status is running, it will not be evict for the `RemoveFailedPods` strategy . but it seems your pod keep restart, if meet requirement...

@sudmis could you show me your descheduler policy config file? it should been evicted for `RemovePodsHavingTooManyRestarts` strategy since your `Restart Count` is so high.