From 28e1180fd4190cd55c65334ef8e91bab5c11b552 Mon Sep 17 00:00:00 2001 From: Brad McCoy Date: Tue, 15 Aug 2023 10:59:57 +1000 Subject: [PATCH] update link Signed-off-by: Brad McCoy --- content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md index 015c11f7b7..02a692129f 100644 --- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md +++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md @@ -138,7 +138,7 @@ CDI provides a standardized way of injecting complex devices into a container (i ## API awareness of sidecar containers (alpha) {#sidecar-init-containers} -Kubernetes 1.28 introduces an alpha `restartPolicy` field for [init containers](/docs/concepts/workloads/pods/init-containers/), +Kubernetes 1.28 introduces an alpha `restartPolicy` field for [init containers](https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/pods/init-containers.md), and uses that to indicate when an init container is also a _sidecar container_. The will start init containers with `restartPolicy: Always` in the order they are defined, along with other init containers. Instead of waiting for that sidecar container to complete before starting the main container(s) for the Pod, the kubelet only waits for the sidecar init container to have started.