Should the documentation example to create the priorityClass be changed to reflect in the apiVersion the most recent API? scheduling.k8s.io/v1 instead of scheduling.k8s.io/v1beta1 In https://docs.openshift.com/container-platform/4.6/nodes/pods/nodes-pods-priority.html#nodes-pods-priority Example to create the priorityClass: cat <<EOF > pc.yaml apiVersion: scheduling.k8s.io/v1beta1 kind: PriorityClass metadata: name: high-priority value: 1000000 globalDefault: false description: "This priority class should be used for XYZ service pods only." EOF -Creating the object gives the warning: [root@bastionhost4 a-ipi-4.6.f5]# oc create -f pc.yaml W0915 17:55:28.810304 8338 warnings.go:67] scheduling.k8s.io/v1beta1 PriorityClass is deprecated in v1.14+, unavailable in v1.22+; use scheduling.k8s.io/v1 PriorityClass priorityclass.scheduling.k8s.io/high-priority created
Luis -- Can you take a look at my PR? Thanks, Michael https://github.com/openshift/openshift-docs/pull/26005
Hi Michael, The PR contains the change I suggested, so it looks good. Thank you Luis
Changes are live: https://docs.openshift.com/container-platform/4.6/nodes/pods/nodes-pods-priority.html#nodes-pods-priority-configuring_nodes-pods-priority