From f5d7f925fc8da554422979a7f44297a5000fc896 Mon Sep 17 00:00:00 2001 From: Mengjiao Liu Date: Thu, 30 May 2024 11:22:23 +0800 Subject: [PATCH] Fixed kubelet option ImageMaximumGCAge example for garbage-collection page --- .../concepts/architecture/garbage-collection.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/architecture/garbage-collection.md b/content/en/docs/concepts/architecture/garbage-collection.md index ffc648014e..41f67b4cbf 100644 --- a/content/en/docs/concepts/architecture/garbage-collection.md +++ b/content/en/docs/concepts/architecture/garbage-collection.md @@ -148,8 +148,17 @@ To configure the setting, enable the `ImageMaximumGCAge` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kubelet, and also set a value for the `ImageMaximumGCAge` field in the kubelet configuration file. -The value is specified as a Kubernetes _duration_; for example, you can set the configuration -field to `3d12h`, which means 3 days and 12 hours. +The value is specified as a Kubernetes _duration_; +Valid time units for the `ImageMaximumGCAge` field in the kubelet configuration file are: +- "ns" for nanoseconds +- "us" or "µs" for microseconds +- "ms" for milliseconds +- "s" for seconds +- "m" for minutes +- "h" for hours + +For example, you can set the configuration field to `12h45m`, +which means 12 hours and 45 minutes. {{< note >}} This feature does not track image usage across kubelet restarts. If the kubelet