OpenShift Init Container: Difference between revisions
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
{{Internal|Kubernetes Init Containers|Kubernetes Init Containers}} | {{Internal|Kubernetes Init Containers|Kubernetes Init Containers}} | ||
=Timeout= | =Timeout= |
Revision as of 01:50, 19 September 2019
External
Internal
Overview
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.