Description of problem

Whenever the LowNodeUtilizationStrategy plugin is in use, the evictionLimits.node setting is not applied and pods are always evicted one by one, as we can see in this log:

nodeutilization.go:334] "Currently, only a single pod eviction is allowed"

Reason is that evictionLimits.node is fed only to the maxNoOfPodsToEvictPerNode setting but not to the numberOfNodes plugin setting, so it defaults to 1, making a effective limit of one pod eviction per node regardless of evictionLimits.node

Version-Release number of selected component (if applicable)

OCP: 4.20.8
cluster-kube-descheduler-operator: 5.3.1

How reproducible

Always

Steps to Reproduce

1. Configure a descheduler profile that uses LowNodeUtilizationStrategy plugin, like KubeVirtRelieveAndMigrate
2. Set evictionLimits.node higher than 1

Actual results

One eviction per node regardless of the setting

Expected results

More than one eviction per node, as per evictionLimits.node setting.

Additional info

None