From cbc8ad69f5687351a605738640e11663eae6f0f4 Mon Sep 17 00:00:00 2001 From: RA489 Date: Thu, 30 Sep 2021 15:25:34 +0530 Subject: [PATCH] explanation of the role of activeDeadlineSeconds in initContainers behaviour --- 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 edf9407845..43d23d3a0a 100644 --- a/content/en/docs/concepts/workloads/pods/init-containers.md +++ b/content/en/docs/concepts/workloads/pods/init-containers.md @@ -282,7 +282,7 @@ define readiness distinct from completion. This is enforced during validation. Use `activeDeadlineSeconds` on the Pod to prevent init containers from failing forever. 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. The Pod which is already running correctly would be killed by `activeDeadlineSeconds` if you set.