-
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
apparmor: Add log-enricher support #1298
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1298 +/- ##
==========================================
+ Coverage 43.92% 44.09% +0.17%
==========================================
Files 49 49
Lines 5514 5563 +49
==========================================
+ Hits 2422 2453 +31
- Misses 2972 2991 +19
+ Partials 120 119 -1 |
Signed-off-by: Paulo Gomes <pjbgf@linux.com>
Signed-off-by: Paulo Gomes <pjbgf@linux.com>
7635322
to
e1479e5
Compare
/test pull-security-profiles-operator-test-e2e |
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.
Awesome work, thank you!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JAORMX, pjbgf, saschagrunert 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
As part of making AppArmor a first class citizen within SPO, the log enrichment features needs to be improved, so that user can have a better view of AppArmor operations across the cluster.
Show AppArmor profiles being reloaded
What pod loaded a new or replaced an existing AppArmor into the node:
Normal AppArmor Entries
Entries include
extra
to expand on additional information:Which issue(s) this PR fixes:
Relates to #718
Does this PR have test?
Yes
Special notes for your reviewer:
Does this PR introduce a user-facing change?