-
Notifications
You must be signed in to change notification settings - Fork 321
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
adding cel for allow-privilege-escalation #503
adding cel for allow-privilege-escalation #503
Conversation
Signed-off-by: Max Smythe <[email protected]>
library/pod-security-policy/allow-privilege-escalation/template.yaml
Outdated
Show resolved
Hide resolved
…e.yaml Co-authored-by: Rita Zhang <[email protected]> Signed-off-by: Max Smythe <[email protected]>
Signed-off-by: Max Smythe <[email protected]>
Signed-off-by: Max Smythe <[email protected]>
Signed-off-by: Max Smythe <[email protected]>
214b7c7
to
fc226c5
Compare
library/pod-security-policy/allow-privilege-escalation/template.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Max Smythe <[email protected]>
Signed-off-by: Max Smythe <[email protected]>
bumped minor version |
@maxsmythe Just confirming, this PR is ready for review right? not a draft. |
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.
cel LGTM
@ritazh Right, no longer a draft, but curious why checks were canceled |
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.
LGTM
What this PR does / why we need it:
This converts K8sAllowPrivilegeEscalation to use CEL in addition to Rego.
Which issue(s) does this PR fix (optional, using
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when the PR gets merged):Fixes #541
Special notes for your reviewer: