From 8e109008343ebf08edfa7f6689846cadc00194c6 Mon Sep 17 00:00:00 2001 From: Zhang Yong Date: Wed, 30 Dec 2020 11:16:15 +0800 Subject: [PATCH] fix init-Container status describe fault --- content/en/docs/concepts/workloads/pods/init-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md index 08d6e0fa0f..869ba66f66 100644 --- a/content/en/docs/concepts/workloads/pods/init-containers.md +++ b/content/en/docs/concepts/workloads/pods/init-containers.md @@ -257,7 +257,7 @@ if the Pod `restartPolicy` is set to Always, the init containers use A Pod cannot be `Ready` until all init containers have succeeded. The ports on an init container are not aggregated under a Service. A Pod that is initializing -is in the `Pending` state but should have a condition `Initialized` set to true. +is in the `Pending` state but should have a condition `Initialized` set to false. If the Pod [restarts](#pod-restart-reasons), or is restarted, all init containers must execute again.