pkdone
commented
6 years ago Hi, thanks for the notes. The scripts actually use the disks I explicitly create for the PVs/PVCs. What is actually redundant is the line "kubectl apply -f ../resources/gce-ssd-storageclass.yaml" in genrate.sh to craete a storage class. This is only needed if the Dynamic PVCs, but in my example I create the disks explicitly (partly to ensure XFS is used - may not be required anymore?). I've commented out that line with an explanation (I've left it in with a comment though as its a useful reference point for people to see). Both methods do result in persistent volume claims which are tolerant of recycling StatefulSet pods, I've just made it more explicit which method I'm using (Static PVs vs Dynamic PVs). See below which shows how the explicitly created disks via PVs are being used for the PVCs.. Thanks Paul
kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE data-volume-4g-1 4Gi RWO Retain Bound default/mongo-configdb-persistent-storage-claim-mongod-configdb-2 fast 2m data-volume-4g-2 4Gi RWO Retain Bound default/mongo-configdb-persistent-storage-claim-mongod-configdb-0 fast 2m data-volume-4g-3 4Gi RWO Retain Bound default/mongo-configdb-persistent-storage-claim-mongod-configdb-1 fast 2m data-volume-8g-1 8Gi RWO Retain Bound default/mongo-shard1-persistent-storage-claim-mongod-shard1-0 fast 2m data-volume-8g-2 8Gi RWO Retain Bound default/mongo-shard2-persistent-storage-claim-mongod-shard2-2 fast 2m data-volume-8g-3 8Gi RWO Retain Bound default/mongo-shard2-persistent-storage-claim-mongod-shard2-0 fast 2m data-volume-8g-4 8Gi RWO Retain Bound default/mongo-shard3-persistent-storage-claim-mongod-shard3-1 fast 2m data-volume-8g-5 8Gi RWO Retain Bound default/mongo-shard1-persistent-storage-claim-mongod-shard1-1 fast 2m data-volume-8g-6 8Gi RWO Retain Bound default/mongo-shard2-persistent-storage-claim-mongod-shard2-1 fast 2m data-volume-8g-7 8Gi RWO Retain Bound default/mongo-shard3-persistent-storage-claim-mongod-shard3-2 fast 2m data-volume-8g-8 8Gi RWO Retain Bound default/mongo-shard1-persistent-storage-claim-mongod-shard1-2 fast 2m data-volume-8g-9 8Gi RWO Retain Bound default/mongo-shard3-persistent-storage-claim-mongod-shard3-0 fast 2m
marekaf
Hi, it seems the created pd is never used.
gcloud compute disks create --size 8GB --type pd-ssd pd-ssd-disk-8g-$ithis creates a persistent disk, however, later when creating persistentVolumeClaim and pod requesting a persistent volume, it creates its own persistentVolume with autogenerated name and the former pd just hangs there. I believe the point was to have a persistentVolume (to not lose the data) which will be named likepd-ssd-disk-8g-$iand that doesn't work. I may submit a PR if you want. Just tell me if you prefer naming the pds as intented or its not important and we can just delete the loops with pd creations. Thanks for the repo and blog btw! It was really helpful.