-
Couldn't load subscription status.
- Fork 41.6k
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.milestone/removedpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/architectureCategorizes an issue or PR as relevant to SIG Architecture.Categorizes an issue or PR as relevant to SIG Architecture.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.sig/instrumentationCategorizes an issue or PR as relevant to SIG Instrumentation.Categorizes an issue or PR as relevant to SIG Instrumentation.
Description
As we work with the new "advanced auditing" API, we're noticing places where the API could be improved. I'm opening this issue to track all the changes we'd like to make to the API when it goes to beta.
API Changes:
-
audit.Event.ObjectRef.APIVersioncurrently holds both the the API group and version, separated by a/. We should break these out into separate fields. - Policy should be able to specify subresources. This could either be a separate field, or allow matching of
/delimited resources (e.g.pods/statusfor the pods resource and status subresource) - ( @ericchiang ) It would be useful to be able to specify resource names in the policy. E.g. ingress controller configmap.
Resourcesin the [GroupResources]
() struct should be changed to a struct that includes Resource + ResourceNames (slice) + (Subresource)type GroupResources struct { -
audit.Event.Metadata.CreationTimestampshows up as null in the json serialized events we output, which looks sloppy. We should consider cleaning this up. One possibility is to get rid of theaudit.Event.Timestampfield, and use CreationTimestamp. - We want to omit the RequestReceived stage in GKE. The policy may be the right place to specify that.
Other Changes:
- feature gate
AdvancedAuditingmoves to beta and defaults to enabled
Postponed to post 1.8.0
- It would be nice to identify the server that sent the audit event, i.e. the aggregator vs. an end-user apiserver. Implementation TBD.
/cc @sttts @soltysh @ericchiang @ihmccreery
Feature: kubernetes/enhancements#22
soltysh
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.milestone/removedpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/architectureCategorizes an issue or PR as relevant to SIG Architecture.Categorizes an issue or PR as relevant to SIG Architecture.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.sig/instrumentationCategorizes an issue or PR as relevant to SIG Instrumentation.Categorizes an issue or PR as relevant to SIG Instrumentation.