Description of problem: when create priorityclass with oc create priorityclass, got error 'error: no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1alpha1"' Version-Release number of selected component (if applicable): # oc version oc v3.11.0-0.13.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://qe-wjiang-master-etcd-1:8443 openshift v3.11.0-0.13.0 kubernetes v1.11.0+d4cacc0 How reproducible: Always Steps to Reproduce: 1. oc create priorityclass dp --value=-1 --global-default=false --description="aoeuoae" 2. 3. Actual results: # oc create priorityclass dp --value=-1 --global-default=false --description="aoeuoae" error: no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1alpha1" Expected results: Should use v1beta1 to do the restapi requests Additional info:
PR https://github.com/kubernetes/kubernetes/pull/65686 has been fixed this but not rebased to release-1.11 for kubernetes
Pick of https://github.com/kubernetes/kubernetes/pull/65686 into Origin: https://github.com/openshift/origin/pull/20624
PR has merged. Moving to MODIFIED
Checked on # oc version oc v3.11.0-0.16.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://qe-wjiang-master-etcd-1:8443 openshift v3.11.0-0.16.0 kubernetes v1.11.0+d4cacc0 and the issue has been fixed
Checked again with # oc version oc v3.11.0-0.22.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://qe-wjiang-master-etcd-1:8443 openshift v3.11.0-0.22.0 kubernetes v1.11.0+d4cacc0 And the issue has been fixed
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-2018:2652