From da8fa820b362d0bc01ec859d6ba17f8c39c8625f Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Wed, 18 Jul 2018 17:29:45 -0400 Subject: [PATCH] statefulset.md - Beta remnants removed (#9522) --- content/en/docs/concepts/workloads/controllers/statefulset.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md index 8688c12bae707..a1fae093cefff 100644 --- a/content/en/docs/concepts/workloads/controllers/statefulset.md +++ b/content/en/docs/concepts/workloads/controllers/statefulset.md @@ -45,7 +45,6 @@ provides a set of stateless replicas. Controllers such as ## Limitations * 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/{{< param "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. * StatefulSets currently require a [Headless Service](/docs/concepts/services-networking/service/#headless-services) to be responsible for the network identity of the Pods. You are responsible for creating this Service.