-
Notifications
You must be signed in to change notification settings - Fork 759
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 labels and metadata in audit logs of resource against which audits run #1977
Comments
I wonder if we should log the contents of the violating resource, or add the option to do so. There may be cases where users wouldn't want certain things logged, like the contents of secrets, so we should be careful how we go about this. |
Adding the option to include labels sounds interesting. Adding contents of the resource sounds too broad and can create privacy and security issues. Definitely interested to see how many people want this feature. Please +1 if you want this and please indicate what additional data you need. |
Adding just the labels should be good enough ! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
@nishant-ui I reckon davis's #2354 addressed the issue here, right? If so, can we close this issue @maxsmythe ? |
SGTM |
The gatekeeper audit pod should have the functionality to emit labels and more details of the resource against which audit ran.
Currently, we get resource name,namespaceetc. It will be good to add labels of the resource as well.
The text was updated successfully, but these errors were encountered: