Tim Bannister
068f8e4c69
- Mention address family in pod concept Preparing to reword this for IPv4 / IPv6 dual stack - Fix capitalization for “cluster”, “container” and “volume” These are not resources you manage via kubectl - Harmonize short descriptions for workload objects in glossary - Expand definition of StatefulSet - Use tooltip for “kubelet” - Revise pod template text - Revise What's Next section
1.2 KiB
Executable File
title, id, date, full_link, short_description, aka, tags
| title | id | date | full_link | short_description | aka | tags | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| StatefulSet | statefulset | 2018-04-12 | /docs/concepts/workloads/controllers/statefulset/ | Manages deployment and scaling of a set of Pods, with durable storage and persistent identifiers for each Pod. |
|
Manages the deployment and scaling of a set of {{< glossary_tooltip text="Pods" term_id="pod" >}}, and provides guarantees about the ordering and uniqueness of these Pods.
Like a {{< glossary_tooltip term_id="deployment" >}}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods. These pods are created from the same spec, but are not interchangeable: each has a persistent identifier that it maintains across any rescheduling.
If you want to use storage volumes to provide persistence for your workload, you can use a StatefulSet as part of the solution. Although individual Pods in a StatefulSet are susceptible to failure, the persistent Pod identifiers make it easier to match existing volumes to the new Pods that replace any that have failed.