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

In links to ref pages, use {{page.version}}.

Browse Source
This commit is contained in:
steveperry-53
2017-07-25 09:37:19 -07:00
committed by Andrew Chen
parent 28f3cfdd4f
commit f9ac865c5f
28 changed files with 98 additions and 98 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/workloads/pods/init-containers.md
+2 -2
View File
@@ -36,7 +36,7 @@ Init Containers are exactly like regular Containers, except:
If an Init Container fails for a Pod, Kubernetes restarts the Pod repeatedly until the Init
Container succeeds. However, if the Pod has a `restartPolicy` of Never, it is not restarted.
To specify a Container as an Init Container, add the `initContainers` field on the PodSpec as a JSON array of objects of type [v1.Container](/docs/api-reference/v1.6/#container-v1-core) alongside the app `containers` array.
To specify a Container as an Init Container, add the `initContainers` field on the PodSpec as a JSON array of objects of type [v1.Container](/docs/api-reference/{{page.version}}/#container-v1-core) alongside the app `containers` array.
The status of the init containers is returned in `status.initContainerStatuses`
field as an array of the container statuses (similar to the `status.containerStatuses`
field).
@@ -185,7 +185,7 @@ pod "myapp-pod" created
$ kubectl get -f myapp.yaml
NAME READY STATUS RESTARTS AGE
myapp-pod 0/1 Init:0/2 0 6m
$ kubectl describe -f myapp.yaml
$ kubectl describe -f myapp.yaml
Name: myapp-pod
Namespace: default
[...]