Skip to content

Commit 7a91341

Browse files
authored
Merge pull request #26007 from yuandongx/patch-20
[zh] fix init container status describe fault
2 parents 253d6ab + 18e7b90 commit 7a91341

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/zh/docs/concepts/workloads/pods/init-containers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -395,7 +395,7 @@ if the Pod `restartPolicy` is set to Always, the init containers use
395395
396396
A Pod cannot be `Ready` until all init containers have succeeded. The ports on an
397397
init container are not aggregated under a Service. A Pod that is initializing
398-
is in the `Pending` state but should have a condition `Initialized` set to true.
398+
is in the `Pending` state but should have a condition `Initialized` set to false.
399399
400400
If the Pod [restarts](#pod-restart-reasons), or is restarted, all init containers
401401
must execute again.
@@ -413,7 +413,7 @@ Pod 的 `restartPolicy` 策略进行重试。
413413
414414
在所有的 Init 容器没有成功之前,Pod 将不会变成 `Ready` 状态。
415415
Init 容器的端口将不会在 Service 中进行聚集。正在初始化中的 Pod 处于 `Pending` 状态,
416-
但会将状况 `Initializing` 设置为 true
416+
但会将状况 `Initializing` 设置为 false
417417
418418
如果 Pod [重启](#pod-restart-reasons),所有 Init 容器必须重新执行。
419419

0 commit comments

Comments
 (0)