3 min read
When we need to have a stateful application running on Kubernetes, we might need to use a StatefulSet. With a StatefulSet, we can manage stateful applications where each pod needs a stable, unique network identity and storage that persists across pod rescheduling. Unlike Deployments, which focus on maintaining a specified number of replicas, StatefulSets ensure each pod is given a unique ordinal index and retains the same identity throughout its lifecycle. If a pod is deleted or a node fails, the replacement pod will maintain the same identity and storage.
04/11/2024
Read more...6 min read
The basic idea behind a StatefulSet is to be able to manage stateful workloads on Kubernetes, unlike Deployments, creating a unique identity for each Pod using a common spec.
With this in mind we might just copy the Pod's template from a Deployment to a StatefulSet object to make it stateful, but it's not always quite that simple.
21/02/2022
Read more...