[minor] fixed the grammar (#4776)
* fix a simple typo fix a simple typo * update notes callout update notes calloutpull/4882/head^2
parent
fe11c3f8f7
commit
f851afc084
|
@ -8,8 +8,9 @@ Since Pods represent processes running on your cluster, Kubernetes provides for
|
|||
1. You send a command or API call to terminate the Pod.
|
||||
1. Kubernetes updates the Pod status to reflect the time after which the Pod is to be considered "dead" (the time of the termination request plus the grace period).
|
||||
1. Kubernetes marks the Pod state as "Terminating" and stops sending traffic to the Pod.
|
||||
1. Kubernetes send a `TERM` signal to the Pod, indicating that the Pod should shut down.
|
||||
1. Kubernetes sends a `TERM` signal to the Pod, indicating that the Pod should shut down.
|
||||
1. When the grace period expires, Kubernetes issues a `SIGKILL` to any processes still running in the Pod.
|
||||
1. Kubernetes removes the Pod from the API server on the Kubernetes Master.
|
||||
|
||||
> **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information.
|
||||
> **Note:** The grace period is configurable; you can set your own grace period when interacting with the cluster to request termination, such as using the `kubectl delete` command. See the [Terminating a Pod]() tutorial for more information.
|
||||
{: .note}
|
||||
|
|
Loading…
Reference in New Issue