whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[zh] synchronize translate init-containers.md

Browse Source
This commit is contained in:
帅进超
2022-01-02 00:09:58 +08:00
parent 76b01c2063
commit 8e503d8d78
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/docs/concepts/workloads/pods/init-containers.md
+2 -2
View File
@@ -465,7 +465,7 @@ Kubernetes 会在校验时强制执行此检查。
<!-- <!--
Use `activeDeadlineSeconds` on the Pod to prevent init containers from failing forever. Use `activeDeadlineSeconds` on the Pod to prevent init containers from failing forever.
The active deadline includes init containers. The active deadline includes init containers.
However it is recommended to use `activeDeadlineSeconds` if user deploy their application However it is recommended to use `activeDeadlineSeconds` only if teams deploy their application
as a Job, because `activeDeadlineSeconds` has an effect even after initContainer finished. as a Job, because `activeDeadlineSeconds` has an effect even after initContainer finished.
The Pod which is already running correctly would be killed by `activeDeadlineSeconds` if you set. The Pod which is already running correctly would be killed by `activeDeadlineSeconds` if you set.
@@ -475,7 +475,7 @@ validation error is thrown for any container sharing a name with another.
在 Pod 上使用 `activeDeadlineSeconds` 和在容器上使用 `livenessProbe` 可以避免 在 Pod 上使用 `activeDeadlineSeconds` 和在容器上使用 `livenessProbe` 可以避免
Init 容器一直重复失败。 Init 容器一直重复失败。
`activeDeadlineSeconds` 时间包含了 Init 容器启动的时间。 `activeDeadlineSeconds` 时间包含了 Init 容器启动的时间。
然而，如果用户将他们的应用程序以 Job 方式部署，建议使用 `activeDeadlineSeconds`， 但建议仅在团队将其应用程序部署为 Job 时才使用 `activeDeadlineSeconds`，
因为 `activeDeadlineSeconds` 在 Init 容器结束后仍有效果。 因为 `activeDeadlineSeconds` 在 Init 容器结束后仍有效果。
如果你设置了 `activeDeadlineSeconds`，已经在正常运行的 Pod 会被杀死。 如果你设置了 `activeDeadlineSeconds`，已经在正常运行的 Pod 会被杀死。