Kubernetes StatefulSet: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
Used for stateful application components, where the application component relies on access to "stable" file storage to maintain state between restarts. As such, [[Kubernetes_Storage_Concepts#local|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 [[Kubernetes_Networking_Concepts#The_DNS_Service|cluster's DNS service]]. | Used for stateful application components, where the application component relies on access to "stable" file storage to maintain state between restarts. As such, [[Kubernetes_Storage_Concepts#local|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 [[Kubernetes_Networking_Concepts#The_DNS_Service|cluster's DNS service]]. | ||
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]]. | |||
=StatefulSet Manifest= | =StatefulSet Manifest= | ||
Revision as of 19:10, 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.