Persistent storage is its own API, you don't need to use it with a satefull set. All of the other properties are implied by stable task names.
And I would guess the doc is a bit of after the fact justification for a design choice already made.
And I would guess the doc is a bit of after the fact justification for a design choice already made.
I believe that's only partially true, since even if one has a PVC in something like a Deployment (the antipattern I see *a lot* in folks new to k8s trying to run mysql or whatever), then "k scale --replicas=10 deploy/my-deploy" will not allocate new PVCs for the new pods
That's why I think StatefulSets are valuable as their own resource type: they represent _future_ storage needs