You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each request can be recorded with an associated "stage". The known stages are:
@@ -162,7 +165,7 @@ script, which generates the audit policy file. You can see most of the audit pol
162
165
## Audit backends
163
166
164
167
Audit backends persist audit events to an external storage.
165
-
[Kube-apiserver][kube-apiserver] out of the box provides two backends:
168
+
Out of the box, the kube-apiserver provides two backends:
166
169
167
170
- Log backend, which writes events to a disk
168
171
- Webhook backend, which sends events to an external API
@@ -173,7 +176,7 @@ In both cases, audit events structure is defined by the API in the
173
176
-->
174
177
## 审计后端 {#audit-backends}
175
178
176
-
审计后端实现将审计事件导出到外部存储。`Kube-apiserver` 提供两个后端:
179
+
审计后端实现将审计事件导出到外部存储。`Kube-apiserver` 默认提供两个后端:
177
180
178
181
- Log 后端,将事件写入到磁盘
179
182
- Webhook 后端,将事件发送到外部 API
@@ -407,7 +410,7 @@ audit policies.
407
410
408
411
### Use fluentd to collect and distribute audit events from log file
409
412
410
-
[Fluentd](http://www.fluentd.org/) is an open source data collector for unified logging layer.
413
+
[Fluentd](https://www.fluentd.org/) is an open source data collector for unified logging layer.
411
414
In this example, we will use fluentd to split audit events by different namespaces.
412
415
-->
413
416
## 日志收集器示例
@@ -570,10 +573,10 @@ different users into different files.
570
573
```
571
574
572
575
<!--
573
-
1. create a [kubeconfig file](/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig/) for kube-apiserver webhook audit backend
576
+
1. create a [kubeconfig file](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/) for kube-apiserver webhook audit backend
0 commit comments