From 4fa4affdcf3e7adb8903e654dbb5ee843c45ff82 Mon Sep 17 00:00:00 2001
From: Able Lv <26692080+able8@users.noreply.github.com>
Date: Sun, 18 Feb 2024 17:34:25 +0800
Subject: [PATCH] Update logging.md

---
 content/en/docs/concepts/cluster-administration/logging.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/cluster-administration/logging.md b/content/en/docs/concepts/cluster-administration/logging.md
index 7b8722537f182..ceffd28b15582 100644
--- a/content/en/docs/concepts/cluster-administration/logging.md
+++ b/content/en/docs/concepts/cluster-administration/logging.md
@@ -97,15 +97,13 @@ The usual way to access this is by running `kubectl logs`.
 
 {{< feature-state for_k8s_version="v1.21" state="stable" >}}
 
-You can configure the kubelet to rotate logs automatically.
-
-If you configure rotation, the kubelet is responsible for rotating container logs and managing the
+The kubelet is responsible for rotating container logs and managing the
 logging directory structure.
 The kubelet sends this information to the container runtime (using CRI),
 and the runtime writes the container logs to the given location.
 
 You can configure two kubelet [configuration settings](/docs/reference/config-api/kubelet-config.v1beta1/),
-`containerLogMaxSize` and `containerLogMaxFiles`,
+`containerLogMaxSize` (default 10Mi) and `containerLogMaxFiles` (default 5),
 using the [kubelet configuration file](/docs/tasks/administer-cluster/kubelet-config-file/).
 These settings let you configure the maximum size for each log file and the maximum number of
 files allowed for each container respectively.