1

I followed the instructions in this post: how to bound a Persistent volume claim with a gcePersistentDisk?

And when I applied that, my PVC did not bind to the PV, instead I got this error in the event list:

14s         17s          2         test-pvc.155b8df6bac15b5b   PersistentVolumeClaim               Warning   ProvisioningFailed   persistentvolume-controller   Failed to provision volume with StorageClass "standard": claim.Spec.Selector is not supported for dynamic provisioning on GCE

I found a github posting that suggested something that would fix this:

https://github.com/coreos/prometheus-operator/issues/323#issuecomment-299016953

But unfortunately that made no difference.

Is there a soup-to-nuts doc somewhere telling us exactly how to use PV and PVC to create truly persistent volumes? Specifically where you can shut down the pv and pvc and restore them later, and get all your content back? Because as it seems right now, if you lose your PVC for whatever reason, you lose connection to your volume and there is no way to get it back again.

Colin Fox
  • 53
  • 6
  • Go through the official k8s documentation here - https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims – Praveen Sripati Oct 08 '18 at 06:35
  • Could you please share the YAML configuration for your PV and PVC? It might help to find a solution. – VAS Oct 08 '18 at 20:13
  • VAS - I used the yaml from the first link in my question, specifically, the yaml at the end, where he says he found the solution. I tried that, and got the error I indicated in my question. – Colin Fox Oct 09 '18 at 04:32

1 Answers1

2

The default StorageClass is not compatible with a gcePesistentDisk. Something like this would work:

$ cat <<EOF | kubectl create -f -
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: slow
provisioner: kubernetes.io/gce-pd
parameters:
  type: pd-standard
  replication-type: none
EOF

then on your PVC:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: nfs-pvc
  labels:
    app: test
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: "slow" <== specify the storageClass
  resources:
    requests:
      storage: 2Gi
  selector:
    matchLabels:
      app: test

You can also set "slow" as the default storageClass in which case you wouldn't have to specify it on your PVC:

$ kubectl patch storageclass slow -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
Rico
  • 58,485
  • 12
  • 111
  • 141