From fc3ee1ec3c6ff2c3bf40bb75a1aded5e2b181991 Mon Sep 17 00:00:00 2001
From: CaoShuFeng <1033798960@qq.com>
Date: Tue, 20 Nov 2018 06:39:38 +0800
Subject: [PATCH] advanced audit doc for ModeBlockingStrict (#10203)

---
 content/en/docs/tasks/debug-application-cluster/audit.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/en/docs/tasks/debug-application-cluster/audit.md b/content/en/docs/tasks/debug-application-cluster/audit.md
index 10f8161f2609f..dc6f9054ccc6b 100644
--- a/content/en/docs/tasks/debug-application-cluster/audit.md
+++ b/content/en/docs/tasks/debug-application-cluster/audit.md
@@ -156,6 +156,7 @@ throttling is enabled in `webhook` and disabled in `log`.
 - `--audit-webhook-mode` defines the buffering strategy. One of the following:
   - `batch` - buffer events and asynchronously process them in batches. This is the default.
   - `blocking` - block API server responses on processing each individual event.
+  - `blocking-strict` - Same as blocking, but when there is a failure during audit logging at RequestReceived stage, the whole request to apiserver will fail.
 
 The following flags are used only in the `batch` mode.