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

Add warning. (#1876)

Browse Source
This commit is contained in:
Anirudh Ramanathan
2016-12-07 10:25:44 -08:00
committed by Devin Donnelly
parent b5a695f86b
commit 8a0ff316d0
2 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/abstractions/controllers/statefulsets.md
+2
View File
@@ -155,6 +155,8 @@ This must be done manually.
* Before a scaling operation is applied to a Pod, all of its predecessors must be Running and Ready. * Before a scaling operation is applied to a Pod, all of its predecessors must be Running and Ready.
* Before a Pod is terminated, all of its successors must be completely shutdown. * Before a Pod is terminated, all of its successors must be completely shutdown.
The StatefulSet should not specify a `pod.Spec.TerminationGracePeriodSeconds` of 0. The practice of setting a `pod.Spec.TerminationGracePeriodSeconds` of 0 seconds is unsafe and strongly discouraged. For further explanation, please refer to [force deleting StatefulSet Pods](/docs/tasks/manage-stateful-set/delete-pods/#deleting-pods).
When the web example above is created, three Pods will be deployed in the order When the web example above is created, three Pods will be deployed in the order
web-0, web-1, web-2. web-1 will not be deployed before web-0 is web-0, web-1, web-2. web-1 will not be deployed before web-0 is
[Running and Ready](/docs/user-guide/pod-states), and web-2 will not be deployed until [Running and Ready](/docs/user-guide/pod-states), and web-2 will not be deployed until
docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set.md
+1
View File
@@ -153,6 +153,7 @@ You can now [upgrade Kubernetes nodes](/docs/admin/cluster-management/#upgrading
to Kubernetes version 1.5 or later. This step is optional, but needs to be done after all StatefulSets to Kubernetes version 1.5 or later. This step is optional, but needs to be done after all StatefulSets
are created to adopt PetSets' Pods. are created to adopt PetSets' Pods.
You should be running Node version >= 1.1.0 to run StatefulSets safely. Older versions do not support features which allow the StatefulSet to guarantee that at any time, there is **at most** one Pod with a given identity running in a cluster.
{% endcapture %} {% endcapture %}