我试图将PVC的大小从10G增加到20G,因为我们在1.9.3上运行,在线做它是不存在的。因此,我删除了PVC,并创建了20G的新值作为存储。
pvc-b196868cd-bc75-12e8-ad32-075738325c 100Gi RWO Retain Released myapp/myapp-backup-pv-claim` persistent 4m当我删除时,PV状态打开为"Released“,当我尝试重新创建PVC时,它被创建,但状态为"lost”
myapp-myapp-backup-pv-claim Lost pvc-03b34iknca1-6fr3-19ea-af3b-0073yh2u97f 0 ntfts19-k8s-0101 13m我们使用的是Vsphere卷。尝试了"kubectl patch pv-for-rabbitmq -p '{"spec":{"claimRef":null}}'“的解决方案,这帮助我将pv恢复为”可用“状态,现在PVC处于”挂起“状态。
pvc-b196868cd-bc75-12e8-ad32-075738325c 100Gi RWO Retain Available myapp/myapp-backup-pv-claim` persistent 2m
myapp-myapp-backup-pv-claim Pending pvc-03b34iknca1-6fr3-19ea-af3b-0073yh2u97f 0 ntfts19-k8s-0101 28m PV描述:
Name: myapp-myapp-backup-pv-claim
Namespace: myapp
StorageClass: ntfts19-k8s-0101
Status: Pending
Volume: pvc-03b34iknca1-6fr3-19ea-af3b-0073yh2u97f
Labels: app=my-app
Annotations: <none>
Finalizers: []
Capacity: 0
Access Modes:
Events: <none>PVC描述:
Name: pvc-b196868cd-bc75-12e8-ad32-075738325c
Labels: <none>
Annotations: <none>
StorageClass: persistent
Status: Available
Claim: myapp/myapp-backup-pv-claim
Reclaim Policy: Retain
Access Modes: RWO
Capacity: 100Gi
Message:
Source:
Type: vSphereVolume (a Persistent Disk resource in vSphere)
VolumePath: StoragePolicyName: %v
FSType: [dsNTFTS19_0101] kubevols/kubernetes-dynamic-pvc-b196868cd-bc75-12e8-ad32-075738325c.vmdk
%!(EXTRA string=ext4, string=)Events: <none>发布于 2020-08-26 13:28:00
问题是没有注解,因为这是一个VSphere存储,注解volume.beta.kubernetes.io/storage-provisioner=kubernetes.io/vsphere-volume是强制的。
发布于 2020-08-26 11:46:41
PV和PVC的存储级别应该相同。仅当控制平面可以找到具有相同存储类别的PV时,它才能将PVC与PV绑定。
你的PV有storageClass: ntfts19-k8s-0101,PVC有storageClass: persistent。因此控制平面找不到具有storageClass持久性的匹配PV。
删除并重新创建PVC以匹配PV的存储类别。
https://stackoverflow.com/questions/63578891
复制相似问题