You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -499,6 +499,10 @@ removes the Pod in the API immediately so a new Pod can be created with the same
499
499
name. On the node, Pods that are set to terminate immediately will still be given
500
500
a small grace period before being force killed.
501
501
502
+
{{< caution >}}
503
+
Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.
504
+
{{< /caution >}}
505
+
502
506
If you need to force-delete Pods that are part of a StatefulSet, refer to the task
503
507
documentation for
504
508
[deleting Pods from a StatefulSet](/docs/tasks/run-application/force-delete-stateful-set-pod/).
0 commit comments