Difference between revisions of "Kubernetes Persistent Volume Claim (PVC)"
Jump to navigation
Jump to search
(→Errors) |
|||
| (23 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | * https://kubernetes.io/docs/concepts/storage/persistent-volumes/ | ||
| + | |||
* <code>[[kubectl get pvc]]</code> | * <code>[[kubectl get pvc]]</code> | ||
* <code>[[kubectl get pvc -o yaml]]</code> | * <code>[[kubectl get pvc -o yaml]]</code> | ||
| Line 22: | Line 24: | ||
[[kubectl apply -f your_new_pvc.yml]] | [[kubectl apply -f your_new_pvc.yml]] | ||
persistentvolumeclaim/myclaim created | persistentvolumeclaim/myclaim created | ||
| + | |||
| + | |||
| + | [[kubectl describe pvc]] yourpv | ||
| + | {{kubectl describe pvc example}} | ||
| + | |||
| + | == Errors == | ||
| + | * <code>[[FailedScheduling]] .../... [[Pod has unbound immediate PersistentVolumeClaims]]</code> | ||
| + | * Warning ClaimLost [[persistentvolumeclaim/]]yourclaim [[Bound claim has lost reference to PersistentVolume]]. Data on the volume is lost! [[Cluster has no ready nodes.]] | ||
| + | * <code>0/7 nodes are available: 7 [[pod has unbound immediate PersistentVolumeClaims]]</code> | ||
| + | |||
| + | == News == | ||
| + | * [[K8s v1.31]] Aug 2024 Changes to reclaim policy for PersistentVolumes | ||
== Related terms == | == Related terms == | ||
| − | * <code>[[kind]]: [[PersistentVolume]]</code> | + | * [[Kubernetes Persistent Volumes (PV)]]: <code>[[kind]]: [[PersistentVolume]]</code> |
* <code>[[kind: StorageClass]]</code> | * <code>[[kind: StorageClass]]</code> | ||
* <code>[[kubectl describe deployment]] | grep [[PersistentVolumeClaim]]</code> | * <code>[[kubectl describe deployment]] | grep [[PersistentVolumeClaim]]</code> | ||
| Line 30: | Line 44: | ||
* <code>[[awsElasticBlockStore]]</code> | * <code>[[awsElasticBlockStore]]</code> | ||
* <code>[[kubectl get volumesnapshot]]</code> | * <code>[[kubectl get volumesnapshot]]</code> | ||
| − | + | * [[K8up Kubernetes Backup Operator]] | |
| − | * [[K8up]] | ||
* <code>[[kind: Provisioner]]</code> | * <code>[[kind: Provisioner]]</code> | ||
* <code>[[volumes:]]</code> | * <code>[[volumes:]]</code> | ||
| Line 37: | Line 50: | ||
* [[Data on Kubernetes Community (DoKC)]] | * [[Data on Kubernetes Community (DoKC)]] | ||
* [[DiskPressure]] | * [[DiskPressure]] | ||
| + | * [[persistentvolumeclaim]] "yourpvname" [[not found]]. | ||
| + | * [[Kubernetes Finalizers]] | ||
== Activities == | == Activities == | ||
* [[CKA v1.23]]: [[Understand persistent volume claims primitive]] | * [[CKA v1.23]]: [[Understand persistent volume claims primitive]] | ||
| − | |||
| − | |||
* [[Create a PersistentVolumeClaim]] | * [[Create a PersistentVolumeClaim]] | ||
| + | * [[Create a new volume using: kind: PersistentVolumeClaim]] | ||
| + | |||
* Read https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes | * Read https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes | ||
== See also == | == See also == | ||
* {{PVC}} | * {{PVC}} | ||
| − | * {{ | + | * {{DoKC}} |
[[Category:K8s]] | [[Category:K8s]] | ||
Latest revision as of 14:51, 12 September 2024
kubectl get pvckubectl get pvc -o yamlkubectl describe pvc mysql-pv-claimkubectl describe pvc grafanakubectl patch pvc
kind: PersistentVolumeClaim kind: PersistentVolume kind: StorageClass
error: persistentvolumeclaims "your-elasticsearch-master-0" could not be patched: persistentvolumeclaims "your-elasticsearch-master-0" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize.
ProvisioningFailed
PVC types[edit]
gcePersistentDisk- Cinder (OpenStack)
glusterfs- rbd - Ceph RBD
- Azure File
- Azure Disk
- Portworx
- FlexVolumes
- Container Storage Interface (CSI)
Examples[edit]
kind: PersistentVolumeClaim apiVersion: v1 metadata: name: myclaim spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi # specify new size here
kubectl apply -f your_new_pvc.yml persistentvolumeclaim/myclaim created
kubectl describe pvc yourpv apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" pv.kubernetes.io/bound-by-controller: "yes" volume.beta.kubernetes.io/storage-provisioner: example.com/aws-efs creationTimestamp: "2022-10-27T15:10:12Z" finalizers: - kubernetes.io/pvc-protection managedFields: ... manager: kube-controller-manager operation: Update time: "2022-10-27T15:10:13Z" name: yourpv namespace: mynamespace resourceVersion: "719208361" [[selfLink: /api/v1/namespaces/mynamespace/persistentvolumeclaims/myvoy uid: b3295ba0-0000-123-123-1234567 spec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi storageClassName: efs volumeMode: Filesystem volumeName: pvc-1234-1234-1234-1234-123456789 status: accessModes: - ReadWriteOnce capacity: storage: 5Gi phase: Bound
Errors[edit]
FailedScheduling .../... Pod has unbound immediate PersistentVolumeClaims- Warning ClaimLost persistentvolumeclaim/yourclaim Bound claim has lost reference to PersistentVolume. Data on the volume is lost! Cluster has no ready nodes.
0/7 nodes are available: 7 pod has unbound immediate PersistentVolumeClaims
News[edit]
- K8s v1.31 Aug 2024 Changes to reclaim policy for PersistentVolumes
Related terms[edit]
- Kubernetes Persistent Volumes (PV):
kind: PersistentVolume kind: StorageClasskubectl describe deployment | grep PersistentVolumeClaimaws ec2 describe-volumes | grep -A1 NameawsElasticBlockStorekubectl get volumesnapshot- K8up Kubernetes Backup Operator
kind: Provisionervolumes:- Kubernetes HostPath volume provider
- Data on Kubernetes Community (DoKC)
- DiskPressure
- persistentvolumeclaim "yourpvname" not found.
- Kubernetes Finalizers
Activities[edit]
- CKA v1.23: Understand persistent volume claims primitive
- Create a PersistentVolumeClaim
- Create a new volume using: kind: PersistentVolumeClaim
See also[edit]
Advertising:
