From ed7c4e7046c0b02df3f7e133a62fe17fe2ac2f53 Mon Sep 17 00:00:00 2001 From: pacoxu Date: Wed, 17 Mar 2021 11:34:40 +0800 Subject: [PATCH] init container image change or container GC will not restart Pod since 1.20 Signed-off-by: pacoxu --- .../en/docs/concepts/workloads/pods/init-containers.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md index 363c38a39b..1c67e357e5 100644 --- a/content/en/docs/concepts/workloads/pods/init-containers.md +++ b/content/en/docs/concepts/workloads/pods/init-containers.md @@ -313,16 +313,16 @@ limit, the same as the scheduler. A Pod can restart, causing re-execution of init containers, for the following reasons: -* A user updates the Pod specification, causing the init container image to change. - Any changes to the init container image restarts the Pod. App container image - changes only restart the app container. * The Pod infrastructure container is restarted. This is uncommon and would have to be done by someone with root access to nodes. * All containers in a Pod are terminated while `restartPolicy` is set to Always, forcing a restart, and the init container completion record has been lost due to garbage collection. - +The Pod will not be restarted when the init container image is changed, or the +init container completion record has been lost due to garbage collection. This +applies for Kubernetes v1.20 and later. If you are using an earlier version of +Kubernetes, consult the documentation for the version you are using. ## {{% heading "whatsnext" %}}