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

kubernetes statefulset pvc yaml

I've tried everything I can think of but I've hit a wall trying to I can't seem to get I'm integrating two systems and I'm working on a project and hit a roadblock... I've been struggling with this for a few days now and could really use some help. This might be a silly question, but I recently upgraded my Kubernetes cluster to version 1.25, and now my StatefulSet pods are failing to expose their persistent volumes correctly. The pods are exploring in 'Pending' state, and the events show a `FailedMount` behavior. The relevant part of 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: myapp template: metadata: labels: app: myapp spec: containers: - name: myapp-container image: myapp:latest volumeMounts: - name: myapp-storage mountPath: /data volumeClaimTemplates: - metadata: name: myapp-storage spec: accessModes: [ "ReadWriteOnce" ] resources: requests: storage: 1Gi ``` I double-checked that my storage class is still available and correctly defined, using: ```bash kubectl get storageclass ``` It returns: ``` NAME PROVISIONER AGE standard kubernetes.io/aws-ebs 10d ``` I also verified that the PersistentVolumeClaims (PVCs) created by the StatefulSet are not bound to any PersistentVolumes (PVs) by running: ```bash kubectl get pvc ``` This command shows: ``` NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE myapp-storage-0 Pending 1Gi RWO standard 2m myapp-storage-1 Pending 1Gi RWO standard 2m myapp-storage-2 Pending 1Gi RWO standard 2m ``` I noticed the behavior logs for the pods say: ``` Warning FailedMount 5m (x4 over 10m) kubelet, ip-10-0-1-2.us-west-2.compute.internal MountVolume.SetUp failed for volume "myapp-storage" : want to find the requested volume ``` I suspect the upgrade might have changed some behavior or settings related to PVCs, but I'm not sure where to check next. Any suggestions on how to debug this situation or potential changes in Kubernetes 1.25 that I should be aware of? For context: I'm using Yaml on Linux. I'm working on a service that needs to handle this. Thanks in advance! What are your experiences with this? I'm working with Yaml in a Docker container on Windows 11. Thanks, I really appreciate it! This is my first time working with Yaml 3.9. Thanks for your help in advance!