Description of problem:
Values in the configmap is still seen as null for include & exclude params even after setting the right value

Version-Release number of selected component (if applicable):
[ramakasturinarra@dhcp35-60 openshift-client-linux-4.6.0-0.nightly-2020-09-10-031249]$ ./oc version 
Client Version: 4.6.0-0.nightly-2020-09-10-031249
Server Version: 4.6.0-0.nightly-2020-09-09-040238
Kubernetes Version: v1.19.0-rc.2+068702d


How reproducible:
Always

Steps to Reproduce:
1. Install latest 4.6 cluster
2. Add the podLifeTime strategy as below
strategies:
  - name: PodLifeTime
    params:
    - name: maxPodLifeTimeSeconds
      value: "3600"

3. Now edit the kubedescheduler object and the other params as below
- name: includeNamespaces
      value: my-project


Actual results:
I see that the cluster pod does not get respinned also the values in the configmap does not change.

oc get kubedescheduler cluster -o yaml
===========================================
spec:
  deschedulingIntervalSeconds: 3600
  image: registry.redhat.io/openshift4/ose-descheduler@sha256:ac21a65ec072db9b9c66c1c6aed940428c9313cc7870cc3976bebf3c5772cde7
  strategies:
  - name: PodLifeTime
    params:
    - name: maxPodLifeTimeSeconds
      value: "3600"
    - name: includeNamespaces
      value: my-project

oc get configmap cluster -o yaml
=================================
[ramakasturinarra@dhcp35-60 openshift-client-linux-4.6.0-0.nightly-2020-09-10-031249]$ oc get configmap cluster -o yaml
apiVersion: v1
data:
  policy.yaml: |
    strategies:
      PodLifeTime:
        enabled: true
        params:
          maxPodLifeTimeSeconds: 3600
          namespaces:
            exclude: null
            include: null
          thresholdPriority: null
          thresholdPriorityClassName: ""
kind: ConfigMap
metadata:
  creationTimestamp: "2020-09-10T16:37:56Z"
  managedFields:
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:data:
        .: {}
        f:policy.yaml: {}
      f:metadata:
        f:ownerReferences:
          .: {}
          k:{"uid":"d75acd99-551c-40c7-989d-48b08d2bda90"}:
            .: {}
            f:apiVersion: {}
            f:kind: {}
            f:name: {}
            f:uid: {}
    manager: cluster-kube-descheduler-operator
    operation: Update
    time: "2020-09-10T16:37:56Z"
  name: cluster
  namespace: openshift-kube-descheduler-operator
  ownerReferences:
  - apiVersion: v1beta1
    kind: KubeDescheduler
    name: cluster
    uid: d75acd99-551c-40c7-989d-48b08d2bda90
  resourceVersion: "58283"
  selfLink: /api/v1/namespaces/openshift-kube-descheduler-operator/configmaps/cluster
  uid: 2afd4f20-fb01-4c7f-90f7-094afa866ef2


Expected results:
values of params should be set correctly and should not show null

Additional info:
same thing happens for thresholdPriority & thresholdPriorityClassName as well

spec:
  deschedulingIntervalSeconds: 3600
  image: registry.redhat.io/openshift4/ose-descheduler@sha256:ac21a65ec072db9b9c66c1c6aed940428c9313cc7870cc3976bebf3c5772cde7
  strategies:
  - name: PodLifeTime
    params:
    - name: maxPodLifeTimeSeconds
      value: "3600"
    - name: includeNamespaces
      value: my-project
    - name: thresholdPriorityClassName
      value: system-cluster-critical

[ramakasturinarra@dhcp35-60 openshift-client-linux-4.6.0-0.nightly-2020-09-10-031249]$ oc get configmap cluster -o yaml
apiVersion: v1
data:
  policy.yaml: |
    strategies:
      PodLifeTime:
        enabled: true
        params:
          maxPodLifeTimeSeconds: 3600
          namespaces:
            exclude: null
            include: null
          thresholdPriority: null
          thresholdPriorityClassName: ""