diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-10-22 23:22:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-22 23:22:33 -0700 |
| commit | 1df42ec84bf5539e132a079c4bf331268f5848d6 (patch) | |
| tree | e08a345641ad6474ba1fe0aa07a84cfd163a46aa | |
| parent | 5b0f5763744d41b5e54a34372e302bc5a787cf6b (diff) | |
| parent | 8d42d16dcfcadbb98b9d544c301839dfa85b6876 (diff) | |
Merge pull request #1255 from wjx1995/patch-1
Automatic merge from submit-queue.
Update auditing.md typo
| -rw-r--r-- | contributors/design-proposals/api-machinery/auditing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/api-machinery/auditing.md b/contributors/design-proposals/api-machinery/auditing.md index ff1b9092..b4e1d91e 100644 --- a/contributors/design-proposals/api-machinery/auditing.md +++ b/contributors/design-proposals/api-machinery/auditing.md @@ -80,7 +80,7 @@ When implementing audit logging there are basically two options: 1. put a logging proxy in front of the apiserver 2. integrate audit logging into the apiserver itself -Both approaches have advantages and disadvanteges: +Both approaches have advantages and disadvantages: - **pro proxy**: + keeps complexity out of the apiserver + reuses existing solutions |