Description of problem:

The machine-os-builder deployment manifest does not set the openshift.io/required-scc annotation, which appears to be required for the upgrade conformance suite to pass. The rest of the MCO components currently set this annotation and we can probably use the same setting for the Machine Config Controller (which is restricted-v2). What I'm unsure of is whether this also needs to be set on the builder pods as well and what the appropriate setting would be for that case.

Version-Release number of selected component (if applicable):

How reproducible:

This always occurs in the new CI jobs, e2e-aws-ovn-upgrade-ocb-techpreview and e2e-aws-ovn-upgrade-ocb-conformance-suite-techpreview. Here's two examples from rehearsal failures:

• https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/58241/rehearse-58241-pull-ci-openshift-machine-config-operator-master-e2e-aws-ovn-upgrade-ocb-conformance-suite-techpreview/1866605293140447232
• https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/58241/rehearse-58241-pull-ci-openshift-machine-config-operator-master-e2e-aws-ovn-upgrade-ocb-techpreview/1866605293199167488

Steps to Reproduce:

Run either of the aforementioned CI jobs.

Actual results:

Test [sig-auth] all workloads in ns/openshift-machine-config-operator must set the 'openshift.io/required-scc' annotation fails.

Expected results:

Test{{ [sig-auth] all workloads in ns/openshift-machine-config-operator must set the 'openshift.io/required-scc' annotation}} should pass.

Additional info: