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

Update init containers concept to link to new API reference

Browse Source
This commit is contained in:
Tim Bannister
2021-08-04 22:58:42 +01:00
parent a54e81ece4
commit c1feea756f
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/init-containers.md
+5 -3
View File
@@ -32,9 +32,11 @@ If a Pod's init container fails, the kubelet repeatedly restarts that init conta
However, if the Pod has a `restartPolicy` of Never, and an init container fails during startup of that Pod, Kubernetes treats the overall Pod as failed. However, if the Pod has a `restartPolicy` of Never, and an init container fails during startup of that Pod, Kubernetes treats the overall Pod as failed.
To specify an init container for a Pod, add the `initContainers` field into To specify an init container for a Pod, add the `initContainers` field into
the Pod specification, as an array of objects of type the [Pod specification](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodSpec),
[Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core), as an array of `container` items (similar to the app `containers` field and its contents).
alongside the app `containers` array. See [Container](/docs/reference/kubernetes-api/workload-resources/pod-v1/#Container) in the
API reference for more details.
The status of the init containers is returned in `.status.initContainerStatuses` 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 as an array of the container statuses (similar to the `.status.containerStatuses`
field). field).