From c2fd2d3acaf4e036d72fd7cef51d09620a2cf626 Mon Sep 17 00:00:00 2001 From: Pingan Date: Thu, 8 Feb 2018 01:39:48 +0800 Subject: [PATCH] modify the default update strategy of statefulset (#7270) --- docs/concepts/workloads/controllers/statefulset.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/concepts/workloads/controllers/statefulset.md b/docs/concepts/workloads/controllers/statefulset.md index dde71c613f..146be2b043 100644 --- a/docs/concepts/workloads/controllers/statefulset.md +++ b/docs/concepts/workloads/controllers/statefulset.md @@ -207,8 +207,7 @@ annotations for the Pods in a StatefulSet. ### On Delete -The `OnDelete` update strategy implements the legacy (1.6 and prior) behavior. It is the default -strategy when `spec.updateStrategy` is left unspecified. When a StatefulSet's +The `OnDelete` update strategy implements the legacy (1.6 and prior) behavior. When a StatefulSet's `.spec.updateStrategy.type` is set to `OnDelete`, the StatefulSet controller will not automatically update the Pods in a StatefulSet. Users must manually delete Pods to cause the controller to create new Pods that reflect modifications made to a StatefulSet's `.spec.template`. @@ -216,7 +215,7 @@ create new Pods that reflect modifications made to a StatefulSet's `.spec.templa ### Rolling Updates The `RollingUpdate` update strategy implements automated, rolling update for the Pods in a -StatefulSet. When a StatefulSet's `.spec.updateStrategy.type` is set to `RollingUpdate`, the +StatefulSet. It is the default strategy when `spec.updateStrategy` is left unspecified. When a StatefulSet's `.spec.updateStrategy.type` is set to `RollingUpdate`, the StatefulSet controller will delete and recreate each Pod in the StatefulSet. It will proceed in the same order as Pod termination (from the largest ordinal to the smallest), updating each Pod one at a time. It will wait until an updated Pod is Running and Ready prior to