From 67420be850a06e1827c0721f977e7d7d8dc807bf Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Thu, 30 Mar 2017 01:14:25 +0800 Subject: [PATCH] Fix the URL (#3057) * Fix the pr As same as PR3050 * update to v1.6 update to v1.6 * update to v1.6 update to v1.6 --- docs/concepts/workloads/pods/init-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/pods/init-containers.md b/docs/concepts/workloads/pods/init-containers.md index 70ad89c83e..172d842a4a 100644 --- a/docs/concepts/workloads/pods/init-containers.md +++ b/docs/concepts/workloads/pods/init-containers.md @@ -35,7 +35,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](http://kubernetes.io/docs/api-reference/v1/definitions/#_v1_container) 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/v1.6/#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).