The kube-scheduler (and operator) should be able to parse v1beta1 KubeSchedulerConfiguration types as v1alpha1 and v1alpha2 have been deprecated Note: This bug has been created in order to submit a valid BZ for a 4.5 backport of existing functionality in master. It should already be verifiable by confirming that there are no errors in the kube-scheduler logs that look like this: > no kind \"KubeSchedulerConfiguration\" is registered for version \"kubescheduler.config.k8s.io/v1beta1\" in scheme \"k8s.io/kubernetes/pkg/scheduler/apis/config/scheme/scheme.go:31\"
Verified with the payload below and i see that KubeSchedulerConfiguration version is kubescheduler.config.k8s.io/v1beta1 and --config for all kube-scheduler points to --config=/etc/kubernetes/static-pod-resources/configmaps/config/config.yaml. [knarra@knarra openshift-client-linux-4.7.0-0.nightly-2020-10-13-233709]$ ./oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2020-10-14-020853 True False 162m Cluster version is 4.7.0-0.nightly-2020-10-14-020853 sh-4.4# cat /etc/kubernetes/static-pod-resources/kube-scheduler-pod-3/configmaps/config/config.yaml | jq { "apiVersion": "kubescheduler.config.k8s.io/v1beta1", "clientConnection": { "kubeconfig": "/etc/kubernetes/static-pod-resources/configmaps/scheduler-kubeconfig/kubeconfig" }, "kind": "KubeSchedulerConfiguration", "leaderElection": { "leaderElect": true, "resourceLock": "configmaps", "resourceNamespace": "openshift-kube-scheduler" } } sh-4.4# cat /etc/kubernetes/static-pod-resources/kube-scheduler-pod-5/configmaps/config/config.yaml | jq { "apiVersion": "kubescheduler.config.k8s.io/v1beta1", "clientConnection": { "kubeconfig": "/etc/kubernetes/static-pod-resources/configmaps/scheduler-kubeconfig/kubeconfig" }, "kind": "KubeSchedulerConfiguration", "leaderElection": { "leaderElect": true, "resourceLock": "configmaps", "resourceNamespace": "openshift-kube-scheduler" } } sh-4.4# cat /etc/kubernetes/static-pod-resources/kube-scheduler-pod-4/configmaps/config/config.yaml | jq { "apiVersion": "kubescheduler.config.k8s.io/v1beta1", "clientConnection": { "kubeconfig": "/etc/kubernetes/static-pod-resources/configmaps/scheduler-kubeconfig/kubeconfig" }, "kind": "KubeSchedulerConfiguration", "leaderElection": { "leaderElect": true, "resourceLock": "configmaps", "resourceNamespace": "openshift-kube-scheduler" } } Based on the above 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633