-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AUTH-482: set required-scc for openshift workloads #5310
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: kramaranya <kramaranya15@gmail.com>
@kramaranya: This pull request references AUTH-482 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 either version "4.19." or "openshift-4.19.", but it targets "openshift-4.16" instead. 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. |
/retest |
2 similar comments
/retest |
/retest |
@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. |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bryan-cox, 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:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This PR pins
privileged
SCC for thekubevirt-csi-node
in theopenshift-cluster-csi-drivers
namespace. Pinning ensures the workload explicitly uses the required SCC and prevents unintended security vulnerabilities.This is part of the ongoing task to ensure SCC pinning for all workloads in platform namespaces .
Which issue(s) this PR fixes:
Fixes AUTH-482 and sippy test
Checklist