-
Notifications
You must be signed in to change notification settings - Fork 107
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
BPF Recorder: Add mkdir
hook
#2663
base: main
Are you sure you want to change the base?
Conversation
Hi @mhils. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2663 +/- ##
==========================================
- Coverage 45.50% 41.36% -4.14%
==========================================
Files 79 109 +30
Lines 7782 18231 +10449
==========================================
+ Hits 3541 7541 +4000
- Misses 4099 10192 +6093
- Partials 142 498 +356 |
b774a25
to
a965171
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ccojocar, mhils The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
on some kernels, bpf_d_path isn't available
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds an
mkdir
hook on top of #2662Which issue(s) this PR fixes:
None
Does this PR have test?
Yes
Special notes for your reviewer:
Does this PR introduce a user-facing change?