From 1498f297d566c120fc0700746632d7a86ec94fe5 Mon Sep 17 00:00:00 2001 From: Christoph Petrausch <263448+hikhvar@users.noreply.github.com> Date: Thu, 1 Oct 2020 10:43:30 +0200 Subject: [PATCH] Update content/en/docs/concepts/workloads/pods/pod-lifecycle.md Co-authored-by: Tim Bannister --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 29631c4de1..9c74012e8c 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -342,7 +342,8 @@ place, the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} attempts gr shutdown. Typically, the container runtime sends a TERM signal to the main process in each -container. Many container runtimes respect the STOPSIGNAL defined in the container image and send this instead of TERM. +container. Many container runtimes respect the `STOPSIGNAL` value defined in the container +image and send this instead of TERM. Once the grace period has expired, the KILL signal is sent to any remaining processes, and the Pod is then deleted from the {{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}. If the kubelet or the