-
Notifications
You must be signed in to change notification settings - Fork 363
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
Add appliedTo Pod namespace / name to audit logs #5101
Merged
antoninbas
merged 2 commits into
antrea-io:main
from
antoninbas:add-applied-to-pod-name-to-audit-logs
Jun 13, 2023
Merged
Add appliedTo Pod namespace / name to audit logs #5101
antoninbas
merged 2 commits into
antrea-io:main
from
antoninbas:add-applied-to-pod-name-to-audit-logs
Jun 13, 2023
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
That PR has been merged |
antoninbas
force-pushed
the
add-applied-to-pod-name-to-audit-logs
branch
from
June 8, 2023 18:05
7841ccf
to
ff1c882
Compare
antoninbas
added
area/monitoring/auditing
Issues or PRs related to auditing.
area/network-policy
Issues or PRs related to network policies.
api-review
Categorizes an issue or PR as actively needing an API review.
action/release-note
Indicates a PR that should be included in release notes.
labels
Jun 8, 2023
antoninbas
force-pushed
the
add-applied-to-pod-name-to-audit-logs
branch
from
June 8, 2023 21:04
ff1c882
to
00aa223
Compare
tnqn
previously approved these changes
Jun 9, 2023
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
antoninbas
force-pushed
the
add-applied-to-pod-name-to-audit-logs
branch
from
June 9, 2023 17:26
00aa223
to
97559a8
Compare
/test-all |
We include 2 new fields in the audit logs: * the "direction" of the NP rule (`Ingress` or `Egress`) * the reference of the Pod to which the NP rule is applied (as `<namespace>/<name>`). These new fields are *NOT* added to the end of the logs, which could break existing consumers. We also refactor the e2e tests for AuditLogging to improve correctness and readbility. Some logs were not validated properly because of an early "break" statement, and some log fields (e.g., logLabel) were not validated. Fixes antrea-io#3794 Signed-off-by: Antonin Bas <abas@vmware.com>
Signed-off-by: Antonin Bas <abas@vmware.com>
antoninbas
force-pushed
the
add-applied-to-pod-name-to-audit-logs
branch
from
June 9, 2023 18:11
97559a8
to
9569680
Compare
tnqn
approved these changes
Jun 12, 2023
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
/test-all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
action/release-note
Indicates a PR that should be included in release notes.
api-review
Categorizes an issue or PR as actively needing an API review.
area/monitoring/auditing
Issues or PRs related to auditing.
area/network-policy
Issues or PRs related to network policies.
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.
We include 2 new fields in the audit logs:
Ingress
orEgress
)<namespace>/<name>
).These new fields are NOT added to the end of the logs, which could
break existing consumers.
We also refactor the e2e tests for AuditLogging to improve correctness
and readbility. Some logs were not validated properly because of an
early "break" statement, and some log fields (e.g., logLabel) were not
validated.
Fixes #3794