From 87d682052e9dc4e79c8886ae622d26065caab0c1 Mon Sep 17 00:00:00 2001 From: Kenneth Owens Date: Fri, 18 Nov 2016 10:13:23 -0800 Subject: [PATCH] removes legacy claim about mutability of stateful set --- docs/concepts/controllers/statefulsets.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/concepts/controllers/statefulsets.md b/docs/concepts/controllers/statefulsets.md index 8818241f46..3b59025f46 100644 --- a/docs/concepts/controllers/statefulsets.md +++ b/docs/concepts/controllers/statefulsets.md @@ -29,7 +29,6 @@ a set of stateless replicas. ### Limitations * Stateful Set is a beta resource, not available in any Kubernetes release prior to 1.5. * As with all alpha/beta resources, it can be disabled through the `--runtime-config` option passed to the apiserver. -* The only mutable field on a Stateful Set is `replicas` * The storage for a given Pod must either be provisioned by a [Persistent Volume Provisioner](http://releases.k8s.io/{{page.githubbranch}}/examples/experimental/persistent-volume-provisioning/README.md) based on the requested `storage class`, or pre-provisioned by an admin. * Deleting and/or scaling a Stateful Set down will *not* delete the volumes associated with the Stateful Set. This is done to ensure safety first, your data is more valuable than an auto purge of all related Stateful Set resources. **Deleting the Persistent Volume Claims will result in a deletion of the associated volumes**. * Stateful Sets currently require a [Headless Service](/docs/user-guide/services/#headless-services) to be responsible for the network identity of the Pods. The user is responsible for this Service.