PVC is in pending state forever

Hi, I created a PVC on a digitalocean k8s cluster and it was attached to a droplet when I applied the yaml file. I deleted it using kubectl delete -f <path-to-yaml> but when I tried to apply the file again with kubectl apply -f <path-to-yaml> the pvc is in the pending state forever. kubectl describe <pvc> shows the following events:

  Type     Reason                Age                   From                                                                             Message
  ----     ------                ----                  ----                                                                             -------
  Normal   Provisioning          4m22s (x11 over 12m)  dobs.csi.digitalocean.com_master-xxxxxxx  External provisioner is provisioning volume for claim "default/common-pvc"
  Warning  ProvisioningFailed    4m22s (x11 over 12m)  dobs.csi.digitalocean.com_master-xxxxxxx  failed to provision volume with StorageClass "do-block-storage": rpc error: code = InvalidArgument desc = volume capabilities cannot be satisified: unsupported access mode MULTI_NODE_MULTI_WRITER
  Normal   ExternalProvisioning  2m46s (x42 over 12m)  persistentvolume-controller                                                      waiting for a volume to be created, either by external provisioner "" or manually created by system administrator

What did I do wrong and how do I fix it?

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
February 19, 2022


Can you share the PVC yaml definition here?

Keep in mind that as of the time being you can assign a block storage to 1 server at a time only.

For more information about the limitation I could suggest taking a look at the official documentation here: