Since k8s 1.19 is dropping policy config in favor of component config we need to know how many users we have using those configs to better know the impact of this change in 4.6.
Verified bug with the payload below and i see things work as expected. Below are the tests that were run to verify this bug. [ramakasturinarra@dhcp35-60 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-27-234738 True False 9h Cluster version is 4.5.0-0.nightly-2020-05-27-234738 Install 4.5 cluster with the above payload config map set in scheduler cluster object. run command oc get route -A and browse through the prometheus URL And select the parameter cluster_legacy_scheduler_policy and verify that it is shown as below cluster_legacy_scheduler_policy{endpoint="https",instance="10.129.0.9:8443",job="metrics",namespace="openshift-kube-scheduler-operator",pod="openshift-kube-scheduler-operator-7db8fd5d94-x8zdn",service="metrics"} 0 Now create a configmap and use it with the scheduler cluster object. Now go to prometheus UI and select the parameter cluster_legacy_scheduler_policy and click on execute. Verify for the below parameters cluster_legacy_scheduler_policy{endpoint="https",instance="10.129.0.9:8443",job="metrics",namespace="openshift-kube-scheduler-operator",pod="openshift-kube-scheduler-operator-7db8fd5d94-x8zdn",service="metrics"} 1 Based on the above results moving the bug to verified state.
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:2409