-
Notifications
You must be signed in to change notification settings - Fork 332
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
fix: procmount should allow empty values #621
fix: procmount should allow empty values #621
Conversation
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.
Good catch! thanks for the PR!
@Agalin Please sign the commit to fix DCO CI failure. |
688b0d5
to
89a04df
Compare
Sure thing! Added. |
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
Head branch was pushed to by a user without write access
89a04df
to
d49a7a8
Compare
@JaydipGabani looks like it was stuck waiting on automerge, I've rebased it. 🤷 |
Looks like this failure is also happenning on the master branch. |
@Agalin CI issues is now fixed, if you rebase/merge msater CI should pass now. |
There is a mismatch between existing Rego and CEL implementation. Rego allows not providing proc mount value at all while CEL needs a value. Both fail if procMount is set to `null` despite it being a valid value equivalent to not defining the key at all. Signed-off-by: Szymon Soloch <[email protected]>
d49a7a8
to
5519039
Compare
@JaydipGabani rebased, hopefully we'll be able to merge it now. |
What this PR does / why we need it:
There is a mismatch between existing Rego and CEL implementation. Rego allows not providing proc mount value at all while CEL needs a value. Both fail if procMount is set to
null
despite it being a valid value equivalent to not defining the key at all.This mismatch actually causes admission errors after updating to the version with CEL logic for all pods with not defined procMount (i.e. vast majority).
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 #
Special notes for your reviewer: