What are the main differences in management and characteristics between pv Deployments and StatefulSets?

Main differences between Deployments and StatefulSets in Kubernetes:

• State management:

  • Deployments are designed for managing stateless applications. They provide scaling and updating of pods without preserving state.
  • StatefulSets are used for stateful applications, where a unique pod identifier and state preservation are important.

• Pod identification:

  • In Deployments, pods are identical and interchangeable.
  • In StatefulSets, each pod has a unique name with a ordinal number (e.g., web-0, web-1), which is important for applications requiring stable network identities.

• Data storage:

  • Deployments typically use shared Persistent Volumes or do not use persistent storage.
  • StatefulSets ensure each pod is bound to its own Persistent Volume, guaranteeing data persistence across restarts.

• Creation and deletion order:

  • Deployments create and delete pods in parallel.
  • StatefulSets create and delete pods sequentially, which is important for correct state management.

Example of using StatefulSet for a database with persistent storage:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: mysql
spec:
  serviceName: "mysql"
  replicas: 3
  selector:
    matchLabels:
      app: mysql
  template:
    metadata:
      labels:
        app: mysql
    spec:
      containers:
      - name: mysql
        image: mysql:5.7
        volumeMounts:
        - name: mysql-persistent-storage
          mountPath: /var/lib/mysql
  volumeClaimTemplates:
  - metadata:
      name: mysql-persistent-storage
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 1Gi

Thus, the choice between Deployment and StatefulSet depends on the requirements for state and pod identification.