kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Moved pod termination info to a temporary, unlinked file. 

Added title to abstractions overview and pod overview.
This commit is contained in:
Devin Donnelly 2017-01-18 13:30:16 -08:00
parent 92c10a487d
commit f09116b8e3
3 changed files with 17 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/concepts/abstractions/overview.md
View File

@ -1,4 +1,5 @@
---
title: Kubernetes Objects
---
{% capture overview %}

15
docs/concepts/abstractions/pod-termination.md Normal file
View File

@ -0,0 +1,15 @@
---
---
#### <a name="pod-termination"></a> Pod Termination
Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. A typical Pod termination in Kubernetes involves the following steps:
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. 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.

15
docs/concepts/abstractions/pod.md
View File

@ -1,4 +1,5 @@
---
title: Pods
---
{% capture overview %}
@ -9,7 +10,6 @@ This page provides an overview of `Pod`, the smallest deployable object in the K
{:toc}
{% capture body %}
### Understanding Pods
A *Pod* is the basic building block of Kubernetes--the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster.
@ -67,19 +67,6 @@ Some examples of Controllers that contain one or more pods include:
In general, Controllers use a [Pod Template]() that you provide to create the Pods for which it is responsible.
#### <a name="pod-termination"></a> Pod Termination
Since Pods represent processes running on your cluster, Kubernetes provides for *graceful termination* when Pods are no longer needed. Kubernetes implements graceful termination by applying a default *grace period* of 30 seconds from the time that you issue a termination request. A typical Pod termination in Kubernetes involves the following steps:
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. 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.
{% endcapture %}