Skip to content

Commit 447383d

Browse files
authored
Merge pull request #46839 from windsonsea/imagey
[zh] Sync garbage-collection.md
2 parents c1394fa + 6ab3faa commit 447383d

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

content/zh-cn/docs/concepts/architecture/garbage-collection.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -286,17 +286,17 @@ regardless of disk usage. This is a kubelet setting that you configure for each
286286
这是一个可以为每个节点配置的 kubelet 设置。
287287

288288
<!--
289-
To configure the setting, enable the `ImageMaximumGCAge`
289+
To configure the setting, enable the `imageMaximumGCAge`
290290
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kubelet,
291-
and also set a value for the `ImageMaximumGCAge` field in the kubelet configuration file.
291+
and also set a value for the `imageMaximumGCAge` field in the kubelet configuration file.
292292
-->
293-
请为 kubelet 启用 `ImageMaximumGCAge`
293+
请为 kubelet 启用 `imageMaximumGCAge`
294294
[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)
295-
并在 kubelet 配置文件中为 `ImageMaximumGCAge` 字段赋值来配置该设置。
295+
并在 kubelet 配置文件中为 `imageMaximumGCAge` 字段赋值来配置该设置。
296296

297297
<!--
298298
The value is specified as a Kubernetes _duration_;
299-
Valid time units for the `ImageMaximumGCAge` field in the kubelet configuration file are:
299+
Valid time units for the `imageMaximumGCAge` field in the kubelet configuration file are:
300300
- "ns" for nanoseconds
301301
- "us" or "µs" for microseconds
302302
- "ms" for milliseconds
@@ -305,7 +305,7 @@ Valid time units for the `ImageMaximumGCAge` field in the kubelet configuration
305305
- "h" for hours
306306
-->
307307
该值应遵循 Kubernetes **持续时间(Duration)** 格式;
308-
在 kubelet 配置文件中,`ImageMaximumGCAge` 字段的有效时间单位如下:
308+
在 kubelet 配置文件中,`imageMaximumGCAge` 字段的有效时间单位如下:
309309

310310
- "ns" 表示纳秒
311311
- "us" 或 "µs" 表示微秒
@@ -324,13 +324,13 @@ which means 12 hours and 45 minutes.
324324
<!--
325325
This feature does not track image usage across kubelet restarts. If the kubelet
326326
is restarted, the tracked image age is reset, causing the kubelet to wait the full
327-
`ImageMaximumGCAge` duration before qualifying images for garbage collection
327+
`imageMaximumGCAge` duration before qualifying images for garbage collection
328328
based on image age.
329329
-->
330330
这个特性不会跟踪 kubelet 重新启动后的镜像使用情况。
331331
如果 kubelet 被重新启动,所跟踪的镜像年龄会被重置,
332332
导致 kubelet 在根据镜像年龄进行垃圾收集时需要等待完整的
333-
`ImageMaximumGCAge` 时长。
333+
`imageMaximumGCAge` 时长。
334334
{{< /note>}}
335335

336336
<!--

0 commit comments

Comments
 (0)