From 41d8a76c3c93f2cde5b53646be58d5208cd456fe Mon Sep 17 00:00:00 2001 From: Chao Wang Date: Wed, 12 Dec 2018 08:00:58 +0800 Subject: [PATCH] fix audit backends decription (#11535) --- content/en/docs/tasks/debug-application-cluster/audit.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/debug-application-cluster/audit.md b/content/en/docs/tasks/debug-application-cluster/audit.md index fdceb5c5e7..4897ed4526 100644 --- a/content/en/docs/tasks/debug-application-cluster/audit.md +++ b/content/en/docs/tasks/debug-application-cluster/audit.md @@ -92,13 +92,13 @@ admins constructing their own audit profiles. ## Audit backends Audit backends persist audit events to an external storage. -[Kube-apiserver][kube-apiserver] out of the box provides two backends: +[Kube-apiserver][kube-apiserver] out of the box provides three backends: - Log backend, which writes events to a disk - Webhook backend, which sends events to an external API - Dynamic backend, which configures webhook backends through an AuditSink API object. -In both cases, audit events structure is defined by the API in the +In all cases, audit events structure is defined by the API in the `audit.k8s.io` API group. The current version of the API is [`v1`][auditing-api].