+++ This bug was initially created as a clone of Bug #1817316 +++ Description of problem: I see that the descheduler only honors short hand strategy names like duplicates, interpodaffinity, nodetaints etc where as it should also honor strategies "RemoveDuplicates" , RemovePodsViolatingInterPodAntiAffinity etc. Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-03-24-101858 How reproducible: Always Steps to Reproduce: 1. Install descheduler operator 2. Now set the strategy as "RemoveDuplicates" 3. Actual results: Descheduler does not create any kubedescheduler cluster object with this strategy and it gives below error. and error is seen in the operator logs E0324 16:12:46.123566 1 target_config_reconciler.go:297] key failed with : expected one of the duplicates,interpodantiaffinity,lownodeutilization,nodeaffinity,nodetaints to be enabled but found following invalid strategies RemoveDuplicates Expected results: Descheduler should honor the startegy name "RemoveDuplicates" Additional info: This bug needs to be fixed for 4.4 as descheduler should work with both short hand and actual strategy names.
Mike if you make if for 4.4.0 feel free to change the target release here.
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