👀 Views: 76 💬 Answers: 1 📅 Created: 2025-06-13

kubernetes statefulset pvc yaml

I'm upgrading from an older version and I'm sure I'm missing something obvious here, but This might be a silly question, but I'm experiencing issues with a StatefulSet in Kubernetes (v1.26) where, upon scaling up the replicas, the new pods are not able to attach their Persistent Volumes..... I've defined a `VolumeClaimTemplate` in my StatefulSet, but it's not creating the expected Persistent Volume Claims (PVCs) for the new replicas. Here's the relevant part of my StatefulSet definition: ```yaml apiVersion: apps/v1 kind: StatefulSet metadata: name: my-app spec: serviceName: "my-app" replicas: 3 selector: matchLabels: app: my-app template: metadata: labels: app: my-app spec: containers: - name: my-app image: my-app-image:latest ports: - containerPort: 8080 name: http volumeClaimTemplates: - metadata: name: my-app-storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 10Gi ``` I've already tried the following troubleshooting steps: 1. Verified that my storage class is available and correctly configured. 2. Checked the `kubectl describe statefulset my-app` output, which shows that only the existing PVCs were created, but no new ones for the additional replicas. 3. Looked at the logs for the Kubernetes controller manager, but couldn't find any relevant errors regarding PVC creation. When I scale up the StatefulSet using `kubectl scale statefulset my-app --replicas=5`, I expect that 2 new PVCs should be created corresponding to the new replicas, but I see no new PVCs in the namespace when I run `kubectl get pvc`. The only output I see is: ``` NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE my-app-storage-0 Bound pvc-abc 10Gi RWO standard 5h my-app-storage-1 Bound pvc-def 10Gi RWO standard 5h my-app-storage-2 Bound pvc-ghi 10Gi RWO standard 5h ``` This is quite puzzling, and I’d appreciate any insights into why the PVCs are not being created for the new replicas or if I might be missing a configuration detail. Thanks! Has anyone dealt with something similar? For reference, this is a production microservice. I appreciate any insights!