Description of problem: Since openshift-user-critical priority class can be used by multiple components let's move it to CCO. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
test with payload 4.8.0-0.nightly-2021-04-15-152737, the PR can be merged now #oc get PriorityClass openshift-user-critical -oyaml apiVersion: scheduling.k8s.io/v1 description: This priority class should be used for user facing OpenShift workload pods only. kind: PriorityClass metadata: annotations: include.release.openshift.io/self-managed-high-availability: "true" include.release.openshift.io/single-node-developer: "true" creationTimestamp: "2021-04-15T23:10:07Z" - apiVersion: scheduling.k8s.io/v1 manager: cluster-version-operator operation: Update time: "2021-04-15T23:10:07Z" name: openshift-user-critical resourceVersion: "1589" uid: 9a0fe9cb-7e3b-42e9-a799-f073ec1a89ba preemptionPolicy: PreemptLowerPriority value: 1000000000 When PR is merged, will close the bug
PR 1115 is in 4.8.0-0.nightly-2021-04-17-044339 and later payloads Test with payload 4.8.0-0.nightly-2021-04-19-121657, there PriorityClass openshift-user-critical
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.8.2 bug fix and security 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-2021:2438