Verified the bug with the payload below and did not see any OOMKILL of the scheduler revision pods. [ramakasturinarra@dhcp35-60 cucushift]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2020-06-29-084049 True False 25m Cluster version is 4.3.0-0.nightly-2020-06-29-084049 per PR https://github.com/openshift/library-go/pull/821/files, checked the request resources of the installer and pruner static pods [ramakasturinarra@dhcp35-60 cucushift]$ oc get pod -n $ns $podname -o json | jq .spec.containers[0].resources { "limits": { "cpu": "150m", "memory": "100M" }, "requests": { "cpu": "150m", "memory": "100M" } } [ramakasturinarra@dhcp35-60 cucushift]$ ns="openshift-kube-scheduler" [ramakasturinarra@dhcp35-60 cucushift]$ podname=$(oc get pods -n $ns | grep revision-pruner | head -1 | cut -d " " -f1) [ramakasturinarra@dhcp35-60 cucushift]$ oc get pod -n $ns $podname -o json | jq .spec.containers[0].resources { "limits": { "cpu": "150m", "memory": "100M" }, "requests": { "cpu": "150m", "memory": "100M" } } [ramakasturinarra@dhcp35-60 cucushift]$ oc get pod -A | grep -E -v 'Running|Completed' NAMESPACE NAME READY STATUS RESTARTS AGE Based on the above moving the bug to verified state.
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-2020:2805