kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update activeDeadlineSeconds with Pod page

pull/28363/head
RA489 2021-06-10 16:24:23 +05:30
parent 2f4a570f0c
commit 7f9d3e3f90
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/en/docs/concepts/workloads/pods/init-containers.md
View File

@ -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 prohibits `readinessProbe` from being used because init containers cannot
define readiness distinct from completion. This is enforced during validation. define readiness distinct from completion. This is enforced during validation.
Use `activeDeadlineSeconds` on the Pod and `livenessProbe` on the container to Use `activeDeadlineSeconds` on the Pod to prevent init containers from failing forever.
prevent init containers from failing forever. The active deadline includes init The active deadline includes init containers.
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 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. validation error is thrown for any container sharing a name with another.