From 7f9d3e3f90fc61d0c3797950442c06f63ee68833 Mon Sep 17 00:00:00 2001 From: RA489 Date: Thu, 10 Jun 2021 16:24:23 +0530 Subject: [PATCH] Update activeDeadlineSeconds with Pod page --- .../en/docs/concepts/workloads/pods/init-containers.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md index c73bba5517..8ffe3ac288 100644 --- a/content/en/docs/concepts/workloads/pods/init-containers.md +++ b/content/en/docs/concepts/workloads/pods/init-containers.md @@ -278,9 +278,11 @@ Init containers have all of the fields of an app container. However, Kubernetes prohibits `readinessProbe` from being used because init containers cannot define readiness distinct from completion. This is enforced during validation. -Use `activeDeadlineSeconds` on the Pod and `livenessProbe` on the container to -prevent init containers from failing forever. The active deadline includes init -containers. +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 +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. The name of each app and init container in a Pod must be unique; a validation error is thrown for any container sharing a name with another.