whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix cluster auditing task page

Browse Source
This commit is contained in:
Tim Bannister
2020-08-19 00:29:06 +01:00
parent 4f7f778a73
commit 420155905a
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/debug-application-cluster/audit.md
+5 -4
View File
@@ -24,9 +24,10 @@ answer the following questions:
<!-- body --> <!-- body -->
[Kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/) Audit records begin their lifecycle inside the
performs auditing. Each request on each stage [kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/)
of its execution generates an event, which is then pre-processed according to component. Each request on each stage
of its execution generates an audit event, which is then pre-processed according to
a certain policy and written to a backend. The policy determines what's recorded a certain policy and written to a backend. The policy determines what's recorded
and the backends persist the records. The current backend implementations and the backends persist the records. The current backend implementations
include logs files and webhooks. include logs files and webhooks.
@@ -92,7 +93,7 @@ script, which generates the audit policy file. You can see most of the audit pol
## Audit backends ## Audit backends
Audit backends persist audit events to an external storage. Audit backends persist audit events to an external storage.
[Kube-apiserver][kube-apiserver] out of the box provides two backends: Out of the box, the kube-apiserver provides two backends:
- Log backend, which writes events to a disk - Log backend, which writes events to a disk
- Webhook backend, which sends events to an external API - Webhook backend, which sends events to an external API