Description of problem: openshift-kube-scheduler-operator pod is using alpha api Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-07-28-222114 Client Version: version.Info{Major:"4", Minor:"2+", GitVersion:"v4.2.0", GitCommit:"1cca013db", GitTreeState:"clean", BuildDate:"2019-08-01T18:56:59Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.0+1682e38", GitCommit:"1682e38", GitTreeState:"clean", BuildDate:"2019-07-28T20:08:40Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"} OpenShift Version: 4.2.0-0.nightly-2019-07-28-222114 How reproducible: Always Steps to Reproduce: 1.oc project openshift-kube-scheduler-operator 2.oc get pods 3.oc rsh $above_pod 4.find . -name config.yaml -exec cat {} \; Actual results: apiVersion: operator.openshift.io/v1alpha1 kind: GenericOperatorConfig Expected results: alpha api should not be used for prod cluster. Additional info:
Fixed in https://github.com/openshift/cluster-kube-scheduler-operator/pull/163.
Verified the issue have been fixed with 4.2.0-0.nightly-2019-08-08-103722 $ oc rsh openshift-kube-scheduler-operator-dc97ffdc5-vpnhl sh-4.2# find . -name config.yaml -exec cat {} \; apiVersion: operator.openshift.io/v1 kind: GenericOperatorConfig apiVersion: operator.openshift.io/v1 kind: GenericOperatorConfig
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-2019:2922