Amir Alavi
Amir Alavi
So it sounds like you need to enable `evictFailedBarePods` in the default evictor plugin? https://github.com/kubernetes-sigs/descheduler?tab=readme-ov-file#evictor-plugin-configuration-default-evictor
>For now, descheduler evicts the pods which will cause a service interruption. Would you please elaborate on why that is, given that it uses the eviction api. Do you define...
Alternatively, investigating usage of AggregateStatus interpreter 
That sounds good! Once approved/finalized, would you be open to contributions or did you want to lead this change?
If a custom interpreter is enabled [[ref](https://github.com/karmada-io/karmada/blob/eaa3452be89773c518a10ceea6a44d51e614deef/pkg/resourceinterpreter/interpreter.go#L185-L191)], it gets out early and never evaluates default [[ref](https://github.com/karmada-io/karmada/blob/master/pkg/resourceinterpreter/interpreter.go#L213)]
> Hi @a7i would you like to contribute this feature? cc @a7i Yes absolutely! 🎉
`MAX_QUERY_CONCURRENCY` of "2" and "1" did not solve the issue for me
The getTargetNodes in RemoveDuplicates does not respect node resources and can mistakenly evict pods
@bingzheliu `nodeFit` by default is `false` so you may want to enable that. If you are using `descheduler/v1alpha2`, the docs can be found [here](https://github.com/kubernetes-sigs/descheduler/tree/master#evictor-plugin-configuration-default-evictor) to configure the `DefaultEvictor`. ``` profiles:...
The getTargetNodes in RemoveDuplicates does not respect node resources and can mistakenly evict pods
However `nodePorts` is not one of our nodeFit checks. Would you be open to proposing a design for that?