Kubernetes StatefulSet: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
A stateful set makes sure pods are rescheduled in such a way that they retain their [[Kubernetes_Pod_and_Container_Concepts#Pod_Identity|identity]] and [[Kubernetes_Pod_and_Container_Concepts#Pod_State|state]]. | A stateful set makes sure pods are rescheduled in such a way that they retain their [[Kubernetes_Pod_and_Container_Concepts#Pod_Identity|identity]] and [[Kubernetes_Pod_and_Container_Concepts#Pod_State|state]]. | ||
The StatefulSet '''creates''' PersistentVolumeClaims in a manner similar to the one in which it creates pods. More details in [[#StatefuSet_Storage|StatefulSet Storage]] below. | |||
=StatefulSet Manifest= | =StatefulSet Manifest= | ||
Revision as of 19:26, 17 March 2020
External
Internal
Overview
Used for stateful application components, where the application component relies on access to "stable" file storage to maintain state between restarts. As such, local volumes that are directly attached to node hosts, can be used. A StatefulSet and the individual pods the StatefulSet manages are registered with the cluster's DNS service.
A stateful set makes sure pods are rescheduled in such a way that they retain their identity and state.
The StatefulSet creates PersistentVolumeClaims in a manner similar to the one in which it creates pods. More details in StatefulSet Storage below.