OpenShift Init Container: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 6: | Line 6: | ||
* [[OpenShift_Pod_Concepts#Init_Container|OpenShift Pod Concepts]] | * [[OpenShift_Pod_Concepts#Init_Container|OpenShift Pod Concepts]] | ||
* [[ | * [[Kubernetes Init Containers]] | ||
=Life Cycle= | =Life Cycle= |
Revision as of 01:48, 19 September 2019
External
Internal
Life Cycle
Timeout
An init container must finish initializing within ... otherwise it puts the deployment into an error state:
NAME READY STATUS RESTARTS AGE a-1-deploy 0/1 Error 0 13m
Resources
Troubleshooting Init Containers
The logs of init containers can be accessed by identifying the name of the init container with:
oc describe po/a-1-0g52b ... Init Containers: b-dependency-checker: ...
and then getting the logs from that specific container:
oc logs -f -c b-dependency-checker po/a-1-0g52b
Application Dependency Example
TODO: write a step-by-step article.