[release-4.15] OCPBUGS-37549: Set required-scc for openshift workloads

[kramaranya]

OCPBUGS-37549
Cherry-pick of #100

Description of the change:
This PR explicitly sets the required SCC to be used to admit pods of the operator-controller-controller-manager deployment. The SCC chosen is the one that the pods are already getting admitted with, which means that this brings no change to the SCC used.

Motivation for the change:
In some cases, custom SCCs can have higher priority than default SCCs, which means that they will be chosen over the default ones. This can lead to unexpected results; in order to protect openshift workloads from this, we must explicitly pin the required SCC to all our workloads in order to make sure that the expected one will be used.

[openshift-ci-robot]

@kramaranya: This pull request references Jira Issue OCPBUGS-37549, which is invalid:

• expected Jira Issue OCPBUGS-37549 to depend on a bug targeting a version in 4.16.0, 4.16.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

OCPBUGS-37549
Cherry-pick of #100

Description of the change:
This PR explicitly sets the required SCC to be used to admit pods of the operator-controller-controller-manager deployment. The SCC chosen is the one that the pods are already getting admitted with, which means that this brings no change to the SCC used.

Motivation for the change:
In some cases, custom SCCs can have higher priority than default SCCs, which means that they will be chosen over the default ones. This can lead to unexpected results; in order to protect openshift workloads from this, we must explicitly pin the required SCC to all our workloads in order to make sure that the expected one will be used.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[kramaranya]

/jira refresh

[openshift-ci-robot]

@kramaranya: This pull request references Jira Issue OCPBUGS-37549, 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-35007 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-35007 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
• bug has dependents

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@kramaranya: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[everettraven]

/approve
/lgtm

[kevinrizza]

/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, kevinrizza, kramaranya

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:

• DOWNSTREAM_OWNERS [kevinrizza]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[bandrade]

/label cherry-pick-approved

[openshift-ci-robot]

@kramaranya: Jira Issue OCPBUGS-37549: All pull requests linked via external trackers have merged:

• openshift/operator-framework-operator-controller#120

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

In response to this:

OCPBUGS-37549
Cherry-pick of #100

Description of the change:
This PR explicitly sets the required SCC to be used to admit pods of the operator-controller-controller-manager deployment. The SCC chosen is the one that the pods are already getting admitted with, which means that this brings no change to the SCC used.

Motivation for the change:
In some cases, custom SCCs can have higher priority than default SCCs, which means that they will be chosen over the default ones. This can lead to unexpected results; in order to protect openshift workloads from this, we must explicitly pin the required SCC to all our workloads in order to make sure that the expected one will be used.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-operator-controller
This PR has been included in build ose-olm-operator-controller-container-v4.15.0-202407261437.p0.g303b954.assembly.stream.el8.
All builds following this will include this PR.