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:
Fixed in https://github.com/openshift/cluster-kube-descheduler-operator/pull/100
Switching this to 4.5, please verify it against master with a manual deployment (these steps should be sufficient now: https://github.com/openshift/cluster-kube-descheduler-operator#quick-development, no need to go through the index image method if you don't want to) That will allow https://bugzilla.redhat.com/show_bug.cgi?id=1817318 to be backported to 4.4 in https://github.com/openshift/cluster-kube-descheduler-operator/pull/104
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