$ oc get clusterversion oc gNAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-10-14-182021 True False 26h Cluster version is 4.9.0-0.nightly-2021-10-14-182021 $ $ oc get no NAME STATUS ROLES AGE VERSION master-00.kewang-15sno2.qe.devcluster.openshift.com Ready master,worker 26h v1.22.0-rc.0+894a78b The new PrometheusRule starts working, $ oc get PrometheusRule -n openshift-kube-apiserver kube-apiserver-slos-basic NAME AGE kube-apiserver-slos-basic 5h1m Using clusterbuster gives some workload on cluster, $ ./clusterbuster -P server -b 5 -p 2 -D .01 -M 1 -N 3 -r 4 -d 2 -c 6 -m 1000 -v -s 5 -x After one day, the cpu usage of prometheus pod always keeps ~0.25, due to resource retention limitation, only can observe one day, will paste the screen-shot about this.
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 (OpenShift Container Platform 4.9.4 bug fix 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/RHBA-2021:3935
https://github.com/openshift/cluster-kube-apiserver-operator/pull/1242 landed after 4.9.0 and before 4.9.4, as described in comment 9. Updating Target Release to match.