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

Merge pull request #28363 from RA489/update_init 

Update activeDeadlineSeconds with Pod page
This commit is contained in:
Kubernetes Prow Robot 2021-08-09 07:01:31 -07:00 committed by GitHub
parent 34ab657265 7f9d3e3f90
commit 302743eb9d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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

@ -280,9 +280,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.