-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add portworx-restricted scc #988
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #988 +/- ##
==========================================
+ Coverage 77.76% 77.82% +0.05%
==========================================
Files 59 59
Lines 16242 16285 +43
==========================================
+ Hits 12631 12674 +43
Misses 2747 2747
Partials 864 864
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need to validate this on a OCP cluster before merge.
* Add portworx-restricted scc * Add portworx restricted scc to cluster role
What this PR does / why we need it:
Add a scc portworx-restricted, and use it for stork, csi, pvc controller, lighthouse.
Which issue(s) this PR fixes (optional)
Ticket: https://portworx.atlassian.net/browse/PWX-27673
Test:
Upgrade operator with my test image, and delete one pod of each kind, and verify the pod is back to running state. Confirmed "Updating security context constraints" only show 1 time.