From beffce58947c0a4cece5f3e6ca0e82bc126375c0 Mon Sep 17 00:00:00 2001 From: dkarczmarski Date: Wed, 22 Jan 2025 06:03:00 +0100 Subject: [PATCH 1/3] fix: typo in sidecar-containers.md --- content/en/docs/concepts/workloads/pods/sidecar-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/sidecar-containers.md b/content/en/docs/concepts/workloads/pods/sidecar-containers.md index b358ee4c12..c9dc92f9cf 100644 --- a/content/en/docs/concepts/workloads/pods/sidecar-containers.md +++ b/content/en/docs/concepts/workloads/pods/sidecar-containers.md @@ -91,7 +91,7 @@ execute the primary application logic; instead, they provide supporting function the main application. Sidecar containers have their own independent lifecycles. They can be started, stopped, -and restarted independently of app containers. This means you can update, scale, or +and restarted independently of app containers. This means you can update or maintain sidecar containers without affecting the primary application. Sidecar containers share the same network and storage namespaces with the primary From 4c69cb6dadf42e819cb9b2aaa1071cdacaa3a98e Mon Sep 17 00:00:00 2001 From: dkarczmarski Date: Sun, 26 Jan 2025 22:29:01 +0100 Subject: [PATCH 2/3] fix: typo in sidecar-containers.md --- .../en/docs/concepts/workloads/pods/sidecar-containers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/sidecar-containers.md b/content/en/docs/concepts/workloads/pods/sidecar-containers.md index c9dc92f9cf..cfdf67f58e 100644 --- a/content/en/docs/concepts/workloads/pods/sidecar-containers.md +++ b/content/en/docs/concepts/workloads/pods/sidecar-containers.md @@ -97,9 +97,9 @@ maintain sidecar containers without affecting the primary application. Sidecar containers share the same network and storage namespaces with the primary container. This co-location allows them to interact closely and share resources. -From Kubernetes perspective, sidecars graceful termination is less important. -When other containers took all alloted graceful termination time, sidecar containers -will receive the `SIGTERM` following with `SIGKILL` faster than may be expected. +From a Kubernetes perspective, the sidecar container's graceful termination is less important. +When other containers take all allotted graceful termination time, the sidecar containers +will receive the `SIGTERM` signal, followed by the `SIGKILL` signal, before they have time to terminate gracefully. So exit codes different from `0` (`0` indicates successful exit), for sidecar containers are normal on Pod termination and should be generally ignored by the external tooling. From dc618f08d1bd8e7741a2e3050b10b156335093d6 Mon Sep 17 00:00:00 2001 From: dkarczmarski Date: Mon, 27 Jan 2025 14:39:52 +0100 Subject: [PATCH 3/3] fix: typo in sidecar-containers.md --- content/en/docs/concepts/workloads/pods/sidecar-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/sidecar-containers.md b/content/en/docs/concepts/workloads/pods/sidecar-containers.md index cfdf67f58e..72021b8476 100644 --- a/content/en/docs/concepts/workloads/pods/sidecar-containers.md +++ b/content/en/docs/concepts/workloads/pods/sidecar-containers.md @@ -91,7 +91,7 @@ execute the primary application logic; instead, they provide supporting function the main application. Sidecar containers have their own independent lifecycles. They can be started, stopped, -and restarted independently of app containers. This means you can update or +and restarted independently of app containers. This means you can update, scale, or maintain sidecar containers without affecting the primary application. Sidecar containers share the same network and storage namespaces with the primary