https://issues.redhat.com/browse/WRKLDS-300 The Descheduler Operator should provide the ability to include/exclude certain namespaces to the user. It currently has hardcoded logic to exclude all namespaces prefixed with `openshift-` or `kube-`. Customers would like the ability to provide a similar pattern, or specific list. This would be difficult to implement on a per-profile basis without considerable refactoring of the operator CRD, so it should be implemented as a top-level option.
Verified bug with the paylaod below and i see that it works fine, so moving the bug to verified state. [knarra@knarra OpenShift]$ oc get csv -n openshift-kube-descheduler-operator NAME DISPLAY VERSION REPLACES PHASE clusterkubedescheduleroperator.4.11.0-202206030929 Kube Descheduler Operator 4.11.0-202206030929 Succeeded [knarra@knarra OpenShift]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-06-06-025509 True False 13h Cluster version is 4.11.0-0.nightly-2022-06-06-025509 Below cases were tested: ========================== 1) Enable both include/exclude namespaces and verify that descheduler operator does not allow enabling both at the same time 2) Enable excluded namespaces and verify that pods does not get evicted from the excluded namespace even if they meet eviction criteria 3) Enable included namespaces and verified that pod gets evicted from the included namespaces if they meet eviction criteria.
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069