From 1de3ac5a286160fe16bd0dc1a12aaf0bf5ac6c6e Mon Sep 17 00:00:00 2001 From: Rob Franken Date: Tue, 24 Nov 2020 09:10:12 +0100 Subject: [PATCH] Small wording update on Log sanitization docs Follow up to PR #24845, following the remarks kbhawkey had --- .../concepts/cluster-administration/system-logs.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/concepts/cluster-administration/system-logs.md b/content/en/docs/concepts/cluster-administration/system-logs.md index 68aab4f86d..9ccae3adf7 100644 --- a/content/en/docs/concepts/cluster-administration/system-logs.md +++ b/content/en/docs/concepts/cluster-administration/system-logs.md @@ -99,17 +99,17 @@ List of components currently supporting JSON format: Log sanitization might incur significant computation overhead and therefore should not be enabled in production. {{< /warning >}} -The `--experimental-logging-sanitization` controls if a sanitization filter will be installed in klog. +The `--experimental-logging-sanitization` flag enables the klog sanitization filter. If enabled all log arguments are inspected for fields tagged as sensitive data (e.g. passwords, keys, tokens) and logging of these fields will be prevented. List of components currently supporting log sanitization: -* {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}} -* {{< glossary_tooltip term_id="kube-apiserver" text="kube-apiserver" >}} -* {{< glossary_tooltip term_id="kube-scheduler" text="kube-scheduler" >}} -* {{< glossary_tooltip term_id="kubelet" text="kubelet" >}} +* kube-controller-manager +* kube-apiserver +* kube-scheduler +* kubelet {{< note >}} -This is not interacting with user workload logs, so it won't prevent users workloads from leaking sensitive data. +The Log sanitization filter does not prevent user workload logs from leaking sensitive data. {{< /note >}} ### Log verbosity level