rego: fix slightly incorrect sandbox and hugepage mounts enforcement #1625
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sandbox and hugepage mounts come via CRI config in the form:
sandbox://<absolute-path>
, however the existing enforcement and tests expect it to besandbox://<relative-path>
which causes a problem during mount enforcement, when the sandbox prefix is replaced with an additional path separator in the end.Additionally update policy tests.
Signed-off-by: Maksim An maksiman@microsoft.com