modify the default update strategy of statefulset (#7270)
This commit is contained in:
@@ -207,8 +207,7 @@ annotations for the Pods in a StatefulSet.
|
|||||||
|
|
||||||
### On Delete
|
### On Delete
|
||||||
|
|
||||||
The `OnDelete` update strategy implements the legacy (1.6 and prior) behavior. It is the default
|
The `OnDelete` update strategy implements the legacy (1.6 and prior) behavior. When a StatefulSet's
|
||||||
strategy when `spec.updateStrategy` is left unspecified. When a StatefulSet's
|
|
||||||
`.spec.updateStrategy.type` is set to `OnDelete`, the StatefulSet controller will not automatically
|
`.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
|
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`.
|
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
|
### Rolling Updates
|
||||||
|
|
||||||
The `RollingUpdate` update strategy implements automated, rolling update for the Pods in a
|
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
|
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
|
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
|
each Pod one at a time. It will wait until an updated Pod is Running and Ready prior to
|
||||||
|
|||||||
Reference in New Issue
Block a user