AUTH-482: set required-scc for openshift workloads #54
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@liouk: This pull request references AUTH-482 which is a valid jira issue. In response to this:
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. |
|
@liouk: 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/test-infra repository. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kevinrizza, liouk 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:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-olm-operator-container-v4.16.0-202405100946.p0.g27bf70d.assembly.stream.el9 for distgit ose-cluster-olm-operator. |
Description of the change:
This PR explicitly sets the required SCC to be used to admit pods of the
cluster-olm-operatordeployment. 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.