👀 Views: 63 💬 Answers: 1 📅 Created: 2025-06-22

kubernetes statefulset persistent-volumes pvc YAML

I'm testing a new approach and I'm working with an scenario with my Kubernetes StatefulSet where the pods are exploring in the `ContainerCreating` state... I've defined a StatefulSet to manage my database replicas, and it's configured to use Persistent Volume Claims (PVCs) for storage. However, when I deploy the StatefulSet, the pods don't start, and I see the following message in the events: ``` Warning FailedScheduling 2m30s (x6 over 5m) default-scheduler 0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. ``` I've verified that the PVCs are created but remain in a `Pending` state. Here’s the relevant part of my StatefulSet configuration: ```yaml apiVersion: apps/v1 kind: StatefulSet metadata: name: my-database spec: serviceName: "my-database" replicas: 3 selector: matchLabels: app: my-database template: metadata: labels: app: my-database spec: containers: - name: db image: my-database-image:latest ports: - containerPort: 5432 volumeMounts: - name: data mountPath: /var/lib/mydb volumeClaimTemplates: - metadata: name: data spec: accessModes: - ReadWriteOnce resources: requests: storage: 10Gi ``` I've checked that there are PersistentVolumes (PVs) available that should match the PVCs, and they are also in the `Available` state. Here’s the output of `kubectl get pv`: ``` NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-12345678-abcd 10Gi RWO Delete Available my-database/data standard 5m ``` The storage class is set to `standard`, and I've confirmed it exists in the cluster. I tried to manually bind the PVCs to the PVs, but I still can’t get the pods to start. Could there be a misconfiguration in my StatefulSet or the way I'm handling PVCs? What other debugging steps can I take to resolve this scenario? I'm on Ubuntu 22.04 using the latest version of Yaml. Hoping someone can shed some light on this.