whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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
parent 0854666f54 7b27b3a662
commit 85d4c2df52
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/init-containers.md
+5 -2
View File
@@ -245,8 +245,11 @@ init containers. [What's next](#what-s-next) contains a link to a more detailed
## Detailed behavior ## Detailed behavior
During the startup of a Pod, each init container starts in order, after the During Pod startup, the kubelet delays running init containers until the networking
network and volumes are initialized. Each container must exit successfully before 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 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, exits with failure, it is retried according to the Pod `restartPolicy`. However,
if the Pod `restartPolicy` is set to Always, the init containers use if the Pod `restartPolicy` is set to Always, the init containers use