-
Notifications
You must be signed in to change notification settings - Fork 42.8k
Advanced Auditing 1.12 umbrella bug #65266
Copy link
Copy link
Closed
Labels
area/auditkind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.
Milestone
Description
This is a continuation of #60392
API-related changes
- Graduate API to stable upgrade Audit api version to stable #65891
- Integration with admission
- Annotate audit logs in remote admission webhooks
@CaoShuFeng is working on this in support annotations for admission webhook #58679
- Annotate audit logs in remote admission webhooks
- Add user-agent to audit events Add user-agent to audit-logging #64791
Bugfixes and improvements
- Completely remove legacy audit logging Promote AdvancedAuditing to GA #65862
- [Optional] Always retry audit webhook
- [Optional] Dynamic audit configuration
Policy changes
- Add a setting in audit policy that will allow rejecting API request when audit logging fails Add option to k8s apiserver to reject incoming requests upon audit failure #65763
- [Optional] GCE audit policy should be made re-usable by other setups
- [Optional] Audit policy should be tested (e.g. that it includes all core resources, more context)
To discuss
- [Optional] Auditing federation setups
I mostly carried over the unfinished work from 1.11 issue. Two things added: the ability to reject apiserver requests when audit logging fails (configurable via audit policy) and - optionally - recent proposal for dynamic audit configuration.
/kind feature
/sig auth
/area audit
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/auditkind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.