Merge pull request #29868 from RA489/activedeadlinesec

explanation of the role of activeDeadlineSeconds in initContainers be…
This commit is contained in:
Kubernetes Prow Robot
2021-11-08 06:43:00 -08:00
committed by GitHub
@@ -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.