Skip to content

Commit 320dab7

Browse files
committed
[zh-cn] sync controllers/_index.md job.md pods/_index.md
Signed-off-by: xin.li <[email protected]>
1 parent fad5a42 commit 320dab7

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

content/zh-cn/docs/concepts/workloads/controllers/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: "工作负载资源"
2+
title: "工作负载管理"
33
weight: 20
44
simple_list: true
55
---
66
<!--
7-
title: "Workload Resources"
7+
title: "Workload Management"
88
weight: 20
99
simple_list: true
1010
-->

content/zh-cn/docs/concepts/workloads/controllers/job.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -673,7 +673,7 @@ per index.
673673
为此,可以设置 `.spec.backoffLimitPerIndex` 来指定每个索引的最大 Pod 失败次数。
674674

675675
<!--
676-
When the per-index backoff limit is exceeded for an index, Kuberentes considers the index as failed and adds it to the
676+
When the per-index backoff limit is exceeded for an index, Kubernetes considers the index as failed and adds it to the
677677
`.status.failedIndexes` field. The succeeded indexes, those with a successfully
678678
executed pods, are recorded in the `.status.completedIndexes` field, regardless of whether you set
679679
the `backoffLimitPerIndex` field.
@@ -1617,7 +1617,7 @@ the Job status, allowing the Pod to be removed by other controllers or users.
16171617
{{< note >}}
16181618
<!--
16191619
See [My pod stays terminating](/docs/tasks/debug/debug-application/debug-pods/) if you
1620-
observe that pods from a Job are stucked with the tracking finalizer.
1620+
observe that pods from a Job are stuck with the tracking finalizer.
16211621
-->
16221622
如果你发现来自 Job 的某些 Pod 因存在负责跟踪的 Finalizer 而无法正常终止,
16231623
请参阅[我的 Pod 一直处于终止状态](/zh-cn/docs/tasks/debug/debug-application/debug-pods/)

content/zh-cn/docs/concepts/workloads/pods/_index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -213,17 +213,17 @@ Init containers run and complete before the app containers are started.
213213
{{< glossary_tooltip text="应用容器" term_id="app-container" >}}。
214214
Init 容器会在启动应用容器之前运行并完成。
215215

216-
{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
216+
{{< feature-state for_k8s_version="v1.29" state="beta" >}}
217217

218218
<!--
219-
Enabling the `SidecarContainers` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
219+
Enabled by default, the `SidecarContainers` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
220220
allows you to specify `restartPolicy: Always` for init containers.
221221
Setting the `Always` restart policy ensures that the init containers where you set it are
222222
kept running during the entire lifetime of the Pod.
223223
See [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/init-containers/#sidecar-containers-and-restartpolicy)
224224
for more details.
225225
-->
226-
启用 `SidecarContainers` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)允许你为
226+
启用 `SidecarContainers` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)(默认启用)允许你为
227227
Init 容器指定 `restartPolicy: Always`。设置重启策略为 `Always` 会确保 Init 容器在 Pod 的整个生命周期内保持运行。
228228
更多细节参阅[边车容器和重启策略](/zh-cn/docs/concepts/workloads/pods/init-containers/#sidecar-containers-and-restartpolicy)
229229

0 commit comments

Comments
 (0)