From 31de2ea9d748e20220b4a3d22aa127ffa8063214 Mon Sep 17 00:00:00 2001 From: Daniel Shebib Date: Fri, 28 Jun 2024 14:20:32 -0500 Subject: [PATCH] clarify image change restart behavior for sidecar containers --- content/en/docs/concepts/workloads/pods/sidecar-containers.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/concepts/workloads/pods/sidecar-containers.md b/content/en/docs/concepts/workloads/pods/sidecar-containers.md index 261df097bb..b358ee4c12 100644 --- a/content/en/docs/concepts/workloads/pods/sidecar-containers.md +++ b/content/en/docs/concepts/workloads/pods/sidecar-containers.md @@ -121,6 +121,9 @@ Init containers stop before the main containers start up, so init containers can exchange messages with the app container in a Pod. Any data passing is one-way (for example, an init container can put information inside an `emptyDir` volume). +Changing the image of a sidecar container will not cause the Pod to restart, but will +trigger a container restart. + ## Resource sharing within containers {{< comment >}}