From 0fe73a189015e20d826341ed7bd5d214612ecfdc Mon Sep 17 00:00:00 2001 From: Supriya Sirbi Date: Wed, 8 May 2019 15:08:35 +0530 Subject: [PATCH] Clarification of init-container restart reasons #13022 (#14202) * Clarification of init-container restart reasons #13022 * Clarification of init-container restart reasons #13022 * Clarification of init-container restart reasons #13022 --- content/en/docs/concepts/workloads/pods/init-containers.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md index 2c6aeb8ddf..ecbf476be9 100644 --- a/content/en/docs/concepts/workloads/pods/init-containers.md +++ b/content/en/docs/concepts/workloads/pods/init-containers.md @@ -318,8 +318,9 @@ same as the scheduler. A Pod can restart, causing re-execution of Init Containers, for the following reasons: -* A user updates the PodSpec causing the Init Container image to change. - App Container image changes only restart the app Container. +* A user updates the PodSpec 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,