👀 Views: 54 💬 Answers: 1 📅 Created: 2025-06-14

kubernetes statefulsets pod-management YAML

I've looked through the documentation and I'm still confused about I'm experiencing an issue with a StatefulSet where the pod identity seems to be lost after manually deleting a pod... The StatefulSet is designed to maintain stable identities for pods, but when I delete a pod using `kubectl delete pod <pod-name>`, it gets recreated, but the new pod has a different name and claims to be a new entity. My StatefulSet configuration looks like this: ```yaml apiVersion: apps/v1 kind: StatefulSet metadata: name: my-statefulset spec: serviceName: "my-service" replicas: 3 selector: matchLabels: app: my-app template: metadata: labels: app: my-app spec: containers: - name: my-container image: my-image:latest ports: - containerPort: 80 volumeMounts: - name: my-volume mountPath: /data volumeClaimTemplates: - metadata: name: my-volume spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi ``` I expect that when the pod is deleted, the replacement pod should retain the same identity (name) and be able to access the same persistent storage. However, this is not the case. Instead, I'm seeing new pods being created with different names like `my-statefulset-0`, `my-statefulset-1`, etc., and they seem to have new volume claims rather than reusing the existing ones. I have also checked that the `podManagementPolicy` is set to `OrderedReady`, which should maintain the identities in order. I've tried manually scaling down the StatefulSet and then scaling it back up, but the same issue persists. Additionally, I verified that the PersistentVolumeClaims (PVCs) are not being deleted when I delete the pods. The logs show that the StatefulSet controller is behaving as expected, but it seems like there's a disconnect somewhere. What could be causing this issue, and how can I ensure that the StatefulSet pods maintain their identities correctly when deleted? Any help would be appreciated! This is part of a larger web app I'm building. Any ideas what could be causing this? This is part of a larger CLI tool I'm building. How would you solve this?