In env launched with the open PR using cluster-bot, pre-merge-verified the issue would be gone:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.ci.test-2021-08-23-072735-ci-ln-pmv8lxt-latest True False 48m Cluster version is 4.7.0-0.ci.test-2021-08-23-072735-ci-ln-pmv8lxt-latest
Create above k10-k10 SCC. Then delete one pod under openshift-apiserver project. Check the new created pod, it can be Running.
Check YAML of new pod under openshift-apiserver project, it uses system scc:
$ oc get po apiserver-99b48b76b-92nxd -n openshift-apiserver -o yaml | grep scc
Check YAML of all pods under openshift-apiserver project, they set 'runAsUser: 0' for containers 'openshift-apiserver' and 'fix-audit-permissions'
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.7.30 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.