Merge pull request #19731 from pyaillet/doc/init-container-precision

doc: add precision on init container start order
This commit is contained in:
Kubernetes Prow Robot 2020-04-07 08:05:43 -07:00 committed by GitHub
commit 85d4c2df52
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 4 deletions

View File

@ -71,8 +71,8 @@ have some advantages for start-up related code:
a mechanism to block or delay app container startup until a set of preconditions are met. Once
preconditions are met, all of the app containers in a Pod can start in parallel.
* Init containers can securely run utilities or custom code that would otherwise make an app
container image less secure. By keeping unnecessary tools separate you can limit the attack
surface of your app container image.
container image less secure. By keeping unnecessary tools separate you can limit the attack
surface of your app container image.
### Examples
@ -245,8 +245,11 @@ init containers. [What's next](#what-s-next) contains a link to a more detailed
## Detailed behavior
During the startup of a Pod, each init container starts in order, after the
network and volumes are initialized. Each container must exit successfully before
During Pod startup, the kubelet delays running init containers until the networking
and storage are ready. Then the kubelet runs the Pod's init containers in the order
they appear in the Pod's spec.
Each init container must exit successfully before
the next container starts. If a container fails to start due to the runtime or
exits with failure, it is retried according to the Pod `restartPolicy`. However,
if the Pod `restartPolicy` is set to Always, the init containers use