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

Add minReadySeconds to statefulsets

Browse Source
This commit is contained in:
ravisantoshgudimetla
2021-07-14 11:29:00 -04:00
parent a1fd3a2d57
commit 2dff66611f
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/statefulset.md
+10
View File
@@ -228,6 +228,16 @@ and Ready or completely terminated prior to launching or terminating another
Pod. This option only affects the behavior for scaling operations. Updates are not Pod. This option only affects the behavior for scaling operations. Updates are not
affected. affected.
#### Minimum Ready Seconds
{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
`.spec.minReadySeconds` is an optional field that specifies the minimum number of seconds for which a newly
created Pod should be ready without any of its containers crashing, for it to be considered available.
This defaults to 0 (the Pod will be considered available as soon as it is ready). To learn more about when
a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes).
Please note that this field only works if you enable the `StatefulSetMinReadySeconds` feature gate.
## Update Strategies ## Update Strategies
In Kubernetes 1.7 and later, StatefulSet's `.spec.updateStrategy` field allows you to configure In Kubernetes 1.7 and later, StatefulSet's `.spec.updateStrategy` field allows you to configure