[release-4.15] OCPBUGS-37608: set required-scc for openshift workloads

[ShazaAldawamneh]

• [ ] I added CHANGELOG entry for this change.
• [x] No user facing changes, so no entry in CHANGELOG was needed.

This PR sets the required SCC explicitly on each workload in openshift-* namespaces. The SCC chosen is the one that the pods are getting admitted with, so no change expected there. This is to protect the pods from getting admitted with a different custom SCC than the one intended.

OCPBUGS-37608 Manual cherry-pick of #2335

[danielmellado]

/lgtm

[simonpasquier]

/label backport-risk-assessed /approve

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielmellado, ShazaAldawamneh, simonpasquier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/cluster-monitoring-operator/blob/release-4.15/OWNERS)~~ [danielmellado,simonpasquier] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[jan--f]

not sure why it didn't want Simons label. Trying again /label backport-risk-assessed

[simonpasquier]

/retitle [release-4.15] OCPBUGS-37608: set required-scc for openshift workloads

[openshift-ci-robot]

@ShazaAldawamneh: This pull request references Jira Issue OCPBUGS-37608, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.15.z) matches configured target version for branch (4.15.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * release note type set to "Release Note Not Required" * dependent bug [Jira Issue OCPBUGS-36321](https://issues.redhat.com//browse/OCPBUGS-36321) is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-36321](https://issues.redhat.com//browse/OCPBUGS-36321) targets the "4.16.0" version, which is one of the valid target versions: 4.16.0, 4.16.z * bug has dependents

Requesting review from QA contact: /cc @gangwgr

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2420): > > >* [ ] I added CHANGELOG entry for this change. >* [x] No user facing changes, so no entry in CHANGELOG was needed. > >This PR sets the required SCC explicitly on each workload in openshift-* namespaces. The SCC chosen is the one that the pods are getting admitted with, so no change expected there. This is to protect the pods from getting admitted with a different custom SCC than the one intended. > >[OCPBUGS-37608](https://issues.redhat.com/browse/OCPBUGS-37608) >Manual cherry-pick of [#2335](https://github.com/openshift/cluster-monitoring-operator/pull/2335) Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[juzhao]

/label cherry-pick-approved

[openshift-ci[bot]]

@ShazaAldawamneh: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-ci-robot]

@ShazaAldawamneh: Jira Issue OCPBUGS-37608: All pull requests linked via external trackers have merged:

• openshift/cluster-monitoring-operator#2420

Jira Issue OCPBUGS-37608 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2420): > > >* [ ] I added CHANGELOG entry for this change. >* [x] No user facing changes, so no entry in CHANGELOG was needed. > >This PR sets the required SCC explicitly on each workload in openshift-* namespaces. The SCC chosen is the one that the pods are getting admitted with, so no change expected there. This is to protect the pods from getting admitted with a different custom SCC than the one intended. > >[OCPBUGS-37608](https://issues.redhat.com/browse/OCPBUGS-37608) >Manual cherry-pick of [#2335](https://github.com/openshift/cluster-monitoring-operator/pull/2335) Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: cluster-monitoring-operator This PR has been included in build cluster-monitoring-operator-container-v4.15.0-202408071539.p0.gbc352b5.assembly.stream.el9. All builds following this will include this PR.