kind: PersistentVolumeClaim

Kubernetes Persistent Volume Claim (PVC)

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: myclaim
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi # specify new size here

 apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: your-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:

• StorageClassName
• VolumeClaimTemplates:

• kubectl apply -f your_new_pvc.yml

Errors

error: error validating "yourfile": error validating data: 

[ ValidationError(PersistentVolumeClaim.metadata.finalizers): invalid type for 
io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta.finalizers: got "string", expected "array", 

ValidationError(PersistentVolumeClaim): unknown field "name" in 
io.k8s.api.core.v1.PersistentVolumeClaim ]; if you choose to ignore these errors, turn 

validation off with --validate=false

0/3 nodes are available: 3 persistentvolumeclaim "yourstorage" bound to non-existent persistentvolume

Related

• CSI Volume Cloning
• kubectl describe pvc
• kubectl describe pvc my grafana pvc volume
• Kubernetes Finalizers
• StorageClassName

See also

• Kubernetes Persistent Volume Claim (PVC) (kind: PersistentVolumeClaim), Kubernetes Persistent volumes (PV) (kind: PersistentVolume), kubectl describe pvc, kubectl get pvc, ClaimLost, ProvisioningSucceeded, PV access control
• Kubernetes storage, storage classes, PersistentVolume (PV), PVC, CSI, kind: StorageClass, kind: PersistentVolumeClaim, kind: PersistentVolume, kubectl [ get | describe | edit ] pvc, volumeClaimTemplates:, kubectl patch pv, FailedMount, Volume Expansion, Volume Cloning, snapshots, ExtraVolumes, NotTriggerScaleUp, volumePVCDataSource, AllowVolumeExpansion, EKS storage, provisioner, Storage Capacity Tracking, VolumeBinding, VolumeClaimTemplate, storage.k8s.io, CKA Storage, DoKC, EmptyDir, Volume populators, storageclass.kubernetes.io