Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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:
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 "dobs.csi.digitalocean.com" or manually created by system administrator
What did I do wrong and how do I fix it?
indranil
doug.landau
ralph1
AI-LastWish
newuser23
Brett Bibby
a9124199d01b441190d9a64b3bf57e
nandaf89840b3eb242fe5d0371
MassiveGrayStarfish
Stian Mathisen
Cosmo Mathieu
fmillion