Description of problem: I see that even after passing right threshold parameters in the kubescheduler/cluster cluster logs reports saying "no resource threshold is configured" also i see some more params being passed into the configmap even though customer/user do not pass them. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install the kube descheduler operator 2. Now set the lownodeutilization with the params 3. Actual results: I see that the thresholds are passed correctly to configmap/cluster but cluster logs still shows that "I0207 15:06:41.373147 1 lownodeutilization.go:101] no resource threshold is configured" LowNodeUtilization: enabled: true weight: 0 params: noderesourceutilizationthresholds: thresholds: cpu: 10 memory: 20 pods: 30 targetthresholds: cpu: 10 memory: 20 pods: 30 numberofnodes: 3 nodeaffinitytype: [] RemoveDuplicates: enabled: true weight: 0 params: noderesourceutilizationthresholds: thresholds: {} targetthresholds: {} numberofnodes: 0 nodeaffinitytype: [] RemovePodsViolatingInterPodAntiAffinity: enabled: true weight: 0 params: noderesourceutilizationthresholds: thresholds: {} targetthresholds: {} numberofnodes: 0 nodeaffinitytype: [] RemovePodsViolatingNodeAffinity: enabled: true weight: 0 params: noderesourceutilizationthresholds: thresholds: {} targetthresholds: {} numberofnodes: 0 nodeaffinitytype: - requiredDuringSchedulingIgnoredDuringExecution RemovePodsViolatingNodeTaints: enabled: true weight: 0 params: noderesourceutilizationthresholds: thresholds: {} targetthresholds: {} numberofnodes: 0 nodeaffinitytype: [] Expected results: When the thresholds are set descheduler should honor that and the logs should it correctly also configmap should only have params which are passed from the kubescheduler/cluster. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581