From dcc799da4daf8f6747d5fc1f2a05172bd49a5e09 Mon Sep 17 00:00:00 2001 From: Brad McCoy Date: Sat, 5 Aug 2023 07:36:39 +1000 Subject: [PATCH] Update content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md Co-authored-by: Tim Bannister --- content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) 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 92a8c2c7ca..73282bece8 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 @@ -82,9 +82,8 @@ This introduces a restartPolicy field to init containers and uses it to indicate The condition for startup completion will be that the startup probe succeeded (or if no startup probe is defined) and postStart handler is completed. This condition is represented with the field Started of ContainerStatus type. See the section "Pod startup completed condition" for considerations on picking this signal. -The field restartPolicy will only be accepted on init containers. The only supported value now is Always. No other values will be defined. Moreover, the field will be nullable so the default value will be "no value". - -Other values for restartPolicy of containers will not be accepted and containers will follow the logic currently implemented. +For init containers, you can either omit the `restartPolicy` field, or set it to `Always`. Omitting the field +means that you want a true init container that runs to completion before application startup. Sidecar containers do not block Pod completion: if all regular containers are complete, sidecar containers in that Pod will be terminated.