From 63e9bfbe805710d70288040b05e487c6fc938298 Mon Sep 17 00:00:00 2001 From: Dennis Benzinger | SAP Hybris Date: Mon, 18 Dec 2017 18:35:30 +0100 Subject: [PATCH] Clarify that StatefulSet is stable in 1.9 (#6697) --- docs/concepts/workloads/controllers/statefulset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/controllers/statefulset.md b/docs/concepts/workloads/controllers/statefulset.md index d2496f443a..0fd76d4c8d 100644 --- a/docs/concepts/workloads/controllers/statefulset.md +++ b/docs/concepts/workloads/controllers/statefulset.md @@ -41,7 +41,7 @@ provides a set of stateless replicas. Controllers such as ## Limitations -* StatefulSet is a beta resource, not available in any Kubernetes release prior to 1.5. +* StatefulSet was a beta resource prior to 1.9 and not available in any Kubernetes release prior to 1.5. * As with all alpha/beta resources, you can disable StatefulSet through the `--runtime-config` option passed to the apiserver. * The storage for a given Pod must either be provisioned by a [PersistentVolume Provisioner](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/staging/persistent-volume-provisioning/README.md) based on the requested `storage class`, or pre-provisioned by an admin. * Deleting and/or scaling a StatefulSet down will *not* delete the volumes associated with the StatefulSet. This is done to ensure data safety, which is generally more valuable than an automatic purge of all related StatefulSet resources.