When tresholdPriority and thresholdPriorityClassName is enabled together, no error is seen in the operator logs which tells the user that both cannot be enabled at once
    

     [knarra@knarra-thinkpadx1carbon7th openshift-tests-private]$ oc get csv -n openshift-kube-descheduler-operator
NAME                                    DISPLAY                     VERSION   REPLACES                                PHASE
clusterkubedescheduleroperator.v5.1.0   Kube Descheduler Operator   5.1.0     clusterkubedescheduleroperator.v5.0.1   Succeeded

    

     Always
    

    1. Install ocp4.17 cluster
    2.  Install KDO 5.1.0
    3. Create kubeDescheduler cluster as shown below
[knarra@knarra-thinkpadx1carbon7th openshift-tests-private]$ oc get kubedescheduler cluster -n openshift-kube-descheduler-operator -o yaml
apiVersion: operator.openshift.io/v1
kind: KubeDescheduler
metadata:
  creationTimestamp: "2024-09-12T09:50:44Z"
  generation: 2
  name: cluster
  namespace: openshift-kube-descheduler-operator
  resourceVersion: "63067"
  uid: 1c067539-58ac-4c2c-afac-5157f366f53c
spec:
  deschedulingIntervalSeconds: 3600
  logLevel: Normal
  managementState: Managed
  mode: Predictive
  observedConfig:
    servingInfo:
      cipherSuites:
      - TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
      - TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
      - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
      - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
      - TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
      - TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
      minTLSVersion: VersionTLS12
  operatorLogLevel: Normal
  profileCustomizations:
    devLowNodeUtilizationThresholds: Medium
    namespaces: {}
    thresholdPriority: 99
    thresholdPriorityClassName: priorityh
  profiles:
  - AffinityAndTaints
  unsupportedConfigOverrides: null
status:
  conditions:
  - lastTransitionTime: "2024-09-12T09:50:44Z"
    status: "False"
    type: ConfigObservationDegraded
  - lastTransitionTime: "2024-09-12T09:50:46Z"
    status: "False"
    type: ResourceSyncControllerDegraded
  readyReplicas: 0

    

     No error saying thresholdPrioirty and thresholdPriorityClassName cannot be set together shown in the descheduler operator logs
    

     Error should be seen in the descheduler operator logs which reads `key failed with : It is invalid to set both .spec.profileCustomizations.thresholdPriority and .spec.profileCustomizations.ThresholdPriorityClassName fields`
    

    Similarly no error is shown when both include and exclude namespaces are set together.