Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1887936

Summary: Kube-scheduler should be able to parse v1beta1 KubeSchedulerConfig
Product: OpenShift Container Platform Reporter: Mike Dame <mdame>
Component: kube-schedulerAssignee: Mike Dame <mdame>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.7CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1887941 (view as bug list) Environment:
Last Closed: 2021-02-24 15:25:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1887941    

Description Mike Dame 2020-10-13 15:50:12 UTC
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\"

Comment 2 RamaKasturi 2020-10-14 09:35:14 UTC
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.

Comment 5 errata-xmlrpc 2021-02-24 15:25:41 UTC
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