BPF LSM Enforcement for unorchestrated containers #1206
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daemon1024
changed the title
This commit enables support for policy enforcement for unorchestrated containers where BPF LSM is the enforcer Signed-off-by: daemon1024 <[email protected]>
daemon1024
force-pushed
the
bpflsm-container-only
branch
from
03025ed to
bda7a67
Compare
nyrahul
requested changes
Apr 26, 2023
Signed-off-by: daemon1024 <[email protected]>
daemon1024
force-pushed
the
bpflsm-container-only
branch
from
e4cdda0 to
a6c179e
Compare
|
I was hoping we can automate the system tests for this. Can we create another issue and handle it there since it would require provisioning of the resources? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Enable support for policy enforcement for unorchestrated containers where BPF LSM is the enforcer
Purpose of PR?:
Fixes #838
Does this PR introduce a breaking change?
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>