Description of problem:

 
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.8.46 True False 13d Cluster version is 4.8.46
 
Descheduler Operator is running on the cluster and evicting a Pod (
snapshot-controller) that is part of kube-system namespace.
 
$ oc get po -A
NAMESPACE NAME READY STATUS RESTARTS AGE
openshift-kube-descheduler-operator cluster-6c6d74855c-rtqvq 1/1 Running 0 13d
openshift-kube-descheduler-operator descheduler-operator-57c48c55db-m96pp 1/1 Running 0 13d
 
$ oc logs cluster-6c6d74855c-rtqvq -n openshift-kube-descheduler-operator
...
2022-08-22T05:46:04.526697374Z I0822 05:46:04.526675 1 nodeutilization.go:229] "Pods on node" node="master01.caplab3.sfa.se" allPods=49 nonRemovablePods=48 removablePods=1
2022-08-22T05:46:04.526697374Z I0822 05:46:04.526688 1 nodeutilization.go:236] "Evicting pods based on priority, if they have same priority, they'll be evicted based on QoS tiers"
2022-08-22T05:46:04.541018916Z I0822 05:46:04.540972 1 evictions.go:130] "Evicted pod" pod="kube-system/snapshot-controller-7c87dcdfff-sfntd" reason="LowNodeUtilization"
2022-08-22T05:46:04.541173616Z I0822 05:46:04.541152 1 nodeutilization.go:240] "Evicted pods from node" node="master01.caplab3.sfa.se" evictedPods=1 usage=map[cpu:1975m memory:7767Mi pods:48]
 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install descheduler Operator 
2. Default configuration
3.

Actual results:

Descheduler should not be evicting Pods under kube-system namespace 

Expected results:

Additional info: