API-1809: Provide SCC access via RBAC

[cblecker]

Instead of providing SCC access when running tests by modifying the SCC, just use RBAC and the existing system cluster roles

[openshift-ci-robot]

@cblecker: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• e8b28ae|Provide SCC access via RBAC: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@cblecker: This pull request references API-1809 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

Instead of providing SCC access when running tests by modifying the SCC, just use RBAC and the existing system cluster roles

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.

[cblecker]

/test unit integration

[openshift-ci-robot]

@cblecker: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 8fc74ee|UPSTREAM: : Provide SCC access via RBAC: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[cblecker]

/retest-required

[openshift-ci]

@cblecker: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-agnostic-ovn-cmd	8fc74ee	link	false	/test e2e-agnostic-ovn-cmd

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.

[soltysh]

/lgtm
/approve

[soltysh]

/remove-label backports/unvalidated-commits
/label backports/unvalidated-commits

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker, soltysh

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 [soltysh]

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

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-pod-container-v4.16.0-202405062116.p0.g681e46b.assembly.stream.el9 for distgit openshift-enterprise-pod.
All builds following this will include this PR.

[soltysh]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@soltysh: new pull request created: #1962

In response to this:

/cherry-pick release-4.15

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.

[soltysh]

/cherry-pick release-4.14
/cherry-pick release-4.13

[openshift-cherrypick-robot]

@soltysh: new pull request created: #1965

In response to this:

/cherry-pick release-4.14
/cherry-pick release-4.13

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.

[soltysh]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@soltysh: #1959 failed to apply on top of branch "release-4.13":

Applying: UPSTREAM: <carry>: Provide SCC access via RBAC
Using index info to reconstruct a base tree...
A	openshift-hack/e2e/namespace.go
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): openshift-hack/e2e/namespace.go deleted in HEAD and modified in UPSTREAM: <carry>: Provide SCC access via RBAC. Version UPSTREAM: <carry>: Provide SCC access via RBAC of openshift-hack/e2e/namespace.go left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 UPSTREAM: <carry>: Provide SCC access via RBAC
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.13

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.