From 6e64f8498335c42c9facbf93c4407c82024cfc93 Mon Sep 17 00:00:00 2001 From: willise Date: Sat, 9 May 2020 11:03:47 +0800 Subject: [PATCH] docs: Add all probe explanation of init contaners Signed-off-by: willise --- 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 2ecbdd702a9..8565f49bb39 100644 --- a/content/en/docs/concepts/workloads/pods/init-containers.md +++ b/content/en/docs/concepts/workloads/pods/init-containers.md @@ -46,8 +46,8 @@ including resource limits, volumes, and security settings. However, the resource requests and limits for an init container are handled differently, as documented in [Resources](#resources). -Also, init containers do not support readiness probes because they must run to -completion before the Pod can be ready. +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 container sequentially. Each init container must succeed before the next can run.