Skip to content

Commit 794a8ff

Browse files
authored
Merge pull request #27683 from ravisantoshgudimetla/patch-8
Add docs for minReadySeconds in StatefulSet
2 parents 9234f94 + 2dff666 commit 794a8ff

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

content/en/docs/concepts/workloads/controllers/statefulset.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -228,6 +228,16 @@ and Ready or completely terminated prior to launching or terminating another
228228
Pod. This option only affects the behavior for scaling operations. Updates are not
229229
affected.
230230

231+
#### Minimum Ready Seconds
232+
233+
{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
234+
235+
`.spec.minReadySeconds` is an optional field that specifies the minimum number of seconds for which a newly
236+
created Pod should be ready without any of its containers crashing, for it to be considered available.
237+
This defaults to 0 (the Pod will be considered available as soon as it is ready). To learn more about when
238+
a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes).
239+
240+
Please note that this field only works if you enable the `StatefulSetMinReadySeconds` feature gate.
231241
## Update Strategies
232242

233243
In Kubernetes 1.7 and later, StatefulSet's `.spec.updateStrategy` field allows you to configure

0 commit comments

Comments
 (0)