From f7a969fd7b49b9928bef7cb74558b7f546f95c91 Mon Sep 17 00:00:00 2001 From: Maru Newby Date: Thu, 12 Sep 2019 19:00:30 +0200 Subject: [PATCH] Fix title of audit task (#16230) * Fix title of audit task The content the title refers to indicates an intent of describing how to configure auditing for multiple apiservers rather than multiple clusters. * Update content/en/docs/tasks/debug-application-cluster/audit.md Co-Authored-By: Tim Bannister --- content/en/docs/tasks/debug-application-cluster/audit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/debug-application-cluster/audit.md b/content/en/docs/tasks/debug-application-cluster/audit.md index 51471175ad..e8bb3dbda9 100644 --- a/content/en/docs/tasks/debug-application-cluster/audit.md +++ b/content/en/docs/tasks/debug-application-cluster/audit.md @@ -323,7 +323,7 @@ Administrators should be aware that allowing write access to this feature grants Currently, this feature has performance implications for the apiserver in the form of increased cpu and memory usage. This should be nominal for a small number of sinks, and performance impact testing will be done to understand its scope before the API progresses to beta. -## Multi-cluster setup +## Setup for multiple API servers If you're extending the Kubernetes API with the [aggregation layer][kube-aggregator], you can also set up audit logging for the aggregated apiserver. To do this, pass the configuration options in the