Merge pull request #24311 from hikhvar/pod-termination-signal
Clarify the pod termination process.
This commit is contained in:
@@ -342,7 +342,9 @@ place, the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} attempts gr
|
|||||||
shutdown.
|
shutdown.
|
||||||
|
|
||||||
Typically, the container runtime sends a TERM signal to the main process in each
|
Typically, the container runtime sends a TERM signal to the main process in each
|
||||||
container. Once the grace period has expired, the KILL signal is sent to any remaining
|
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
|
processes, and the Pod is then deleted from the
|
||||||
{{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}. If the kubelet or the
|
{{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}. If the kubelet or the
|
||||||
container runtime's management service is restarted while waiting for processes to terminate, the
|
container runtime's management service is restarted while waiting for processes to terminate, the
|
||||||
|
|||||||
Reference in New Issue
Block a user