From 21c57500869878d40f97dfa5228ff916f8c81d17 Mon Sep 17 00:00:00 2001 From: Ader Date: Sat, 19 Dec 2020 14:13:40 +0800 Subject: [PATCH] Fix some typo in init-containers.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixed a typo in manage-resources-containers.md (Kubelet → kubelet) --- content/en/docs/concepts/workloads/pods/init-containers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md index 5c92f07423..08d6e0fa0f 100644 --- a/content/en/docs/concepts/workloads/pods/init-containers.md +++ b/content/en/docs/concepts/workloads/pods/init-containers.md @@ -49,9 +49,9 @@ as documented in [Resources](#resources). Also, init containers do not support `lifecycle`, `livenessProbe`, `readinessProbe`, or `startupProbe` because they must run to completion before the Pod can be ready. -If you specify multiple init containers for a Pod, Kubelet runs each init +If you specify multiple init containers for a Pod, kubelet runs each init container sequentially. Each init container must succeed before the next can run. -When all of the init containers have run to completion, Kubelet initializes +When all of the init containers have run to completion, kubelet initializes the application containers for the Pod and runs them as usual. ## Using init containers