3 ms·
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 gue
by lokar 4y ago
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.
- mdaniel 4y ago> 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. 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
- mcronce 4y agoPersistent storage tied to a specific member of the deployment is a StatefulSet feature. That's likely what they mean by "stable", although I really wish they were more clear about it
- bogomipz 4y agoYour comment makes no sense. Persistent storage is one component of a stateful set. You are not even using correct Kubernetes terminology, I have never once seen the term "stable task name."