From ab40c3c4039e8d33cf6a9d573b72c6163fe6aaa1 Mon Sep 17 00:00:00 2001 From: Michal Wozniak Date: Tue, 15 Nov 2022 17:30:21 +0100 Subject: [PATCH] Rephrased description for TerminationByKubelet --- content/en/docs/concepts/workloads/pods/disruptions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md index 4aaa0c7a2d8db..d55de70444fa6 100644 --- a/content/en/docs/concepts/workloads/pods/disruptions.md +++ b/content/en/docs/concepts/workloads/pods/disruptions.md @@ -260,7 +260,7 @@ indicates one of the following reasons for the Pod termination: : Pod, that is bound to a no longer existing Node, is due to be deleted by [Pod garbage collection](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection). `TerminationByKubelet` -: Kubelet terminates the Pod, because of the {{}} or the [Graceful Node Shutdown](/docs/concepts/architecture/nodes/#graceful-node-shutdown). Pod is due to be deleted by the controller owning the Pod. +: Kubelet terminated the Pod, because of either {{}} or the [graceful node shutdown](/docs/concepts/architecture/nodes/#graceful-node-shutdown). {{< note >}} A Pod disruption might be interrupted. The control plane might re-attempt to