whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add missing text

Browse Source
This commit is contained in:
Ro$k0
2020-10-09 22:17:35 +13:00
parent c92e5d7c5a
commit 6d4fd2ab2b
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+6 -5
View File
@@ -13,7 +13,8 @@ of its primary containers starts OK, and then through either the `Succeeded` or
Whilst a Pod is running, the kubelet is able to restart containers to handle some Whilst a Pod is running, the kubelet is able to restart containers to handle some
kind of faults. Within a Pod, Kubernetes tracks different container kind of faults. Within a Pod, Kubernetes tracks different container
[states](#container-states) and handles [states](#container-states) and determines what action to take to make the Pod
healthy again.
In the Kubernetes API, Pods have both a specification and an actual status. The In the Kubernetes API, Pods have both a specification and an actual status. The
status for a Pod object consists of a set of [Pod conditions](#pod-conditions). status for a Pod object consists of a set of [Pod conditions](#pod-conditions).
@@ -32,7 +33,7 @@ Like individual application containers, Pods are considered to be relatively
ephemeral (rather than durable) entities. Pods are created, assigned a unique ephemeral (rather than durable) entities. Pods are created, assigned a unique
ID ([UID](/docs/concepts/overview/working-with-objects/names/#uids)), and scheduled ID ([UID](/docs/concepts/overview/working-with-objects/names/#uids)), and scheduled
to nodes where they remain until termination (according to restart policy) or to nodes where they remain until termination (according to restart policy) or
deletion. deletion.
If a {{< glossary_tooltip term_id="node" >}} dies, the Pods scheduled to that node If a {{< glossary_tooltip term_id="node" >}} dies, the Pods scheduled to that node
are [scheduled for deletion](#pod-garbage-collection) after a timeout period. are [scheduled for deletion](#pod-garbage-collection) after a timeout period.
@@ -353,9 +354,9 @@ An example flow:
1. You use the `kubectl` tool to manually delete a specific Pod, with the default grace period 1. You use the `kubectl` tool to manually delete a specific Pod, with the default grace period
(30 seconds). (30 seconds).
1. The Pod in the API server is updated with the time beyond which the Pod is considered "dead" 1. The Pod in the API server is updated with the time beyond which the Pod is considered "dead"
along with the grace period. along with the grace period.
If you use `kubectl describe` to check on the Pod you're deleting, that Pod shows up as If you use `kubectl describe` to check on the Pod you're deleting, that Pod shows up as
"Terminating". "Terminating".
On the node where the Pod is running: as soon as the kubelet sees that a Pod has been marked On the node where the Pod is running: as soon as the kubelet sees that a Pod has been marked
as terminating (a graceful shutdown duration has been set), the kubelet begins the local Pod as terminating (a graceful shutdown duration has been set), the kubelet begins the local Pod
shutdown process. shutdown process.
@@ -386,7 +387,7 @@ An example flow:
`SIGKILL` to any processes still running in any container in the Pod. `SIGKILL` to any processes still running in any container in the Pod.
The kubelet also cleans up a hidden `pause` container if that container runtime uses one. The kubelet also cleans up a hidden `pause` container if that container runtime uses one.
1. The kubelet triggers forcible removal of Pod object from the API server, by setting grace period 1. The kubelet triggers forcible removal of Pod object from the API server, by setting grace period
to 0 (immediate deletion). to 0 (immediate deletion).
1. The API server deletes the Pod's API object, which is then no longer visible from any client. 1. The API server deletes the Pod's API object, which is then no longer visible from any client.
### Forced Pod termination {#pod-termination-forced} ### Forced Pod termination {#pod-termination-forced}