"rookieops" volumetype: "replicate:3" provisioner: kubernetes.io/glusterfs reclaimPolicy: Delete allowVolumeExpansion...-n rookieops NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION...结论:如果动态PV要进行扩容需要满足以下条件: 需要是kubernetes支持的存储,开发能力强的也可以自己开发使其支持第三方存储 需要在sc中开启allowVolumeExpansion: true
通常,为了对可扩展的卷提供某种程度的控制,只有存储类 allowVolumeExpansion 参数设置为 true 的动态调配的 PVC 才是可扩展的。...Kubernetes 集群管理员必须编辑适当的 StorageClass 对象,并将 allowVolumeExpansion 字段设置为 true。...: gp2-default provisioner: kubernetes.io/aws-ebs parameters: secretNamespace: "" secretName: "" allowVolumeExpansion
管理员确定底层存储能够支持卷扩展之后,就可以在 StorageClass 对象中设置 allowVolumeExpansion 为 true 来启用这一功能了。...StorageClass metadata: name: standard parameters: type: pd-standard provisioner: kubernetes.io/gce-pd allowVolumeExpansion
# 回收策略,仅支持 Retain / Delete volumeBindingMode: Immediate # 该字段表示立即绑定 allowVolumeExpansion...对象绑定 Delete:删除策略(默认),该策略不保留存储卷 3、存储卷自动扩容 在 StorageClass 对象中添加以下配置,即可在 PV 对象已使用容量达到预设 Capacity 后,可以自动扩容 allowVolumeExpansion
PV Resize的过程: 1.创建存储类:allowVolumeExpansion=true. 2.创建基于allowVolumeExpansion=true存储类的PVC 3.增加PVC的大小 $
get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
启用PersistentVolumeClaimResize后,allowVolumeExpansion字段设置为true的存储类将允许调整大小。
sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
rook-csi-rbd-provisioner csi.storage.k8s.io/node-stage-secret-name: rook-csi-rbd-node csi.storage.k8s.io/fstype: ext4 allowVolumeExpansion...controller-expand-secret-name 和 csi.storage.k8s.io/node-stage-secret-name 分别指定用于身份验证和授权的 Kubernetes 密钥名称,而 allowVolumeExpansion...get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
kubernetes.io/aws-ebs parameters: type: gp2 fsType: ext4 iopsPerGB: "10" reclaimPolicy: Retain allowVolumeExpansion
# kubectl get scNAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
pvc must support resize 发现报与上面一样的错,这是因为要支持动态扩容需要满足两个条件: 后端底层存储支持卷扩展(后端存储保证足够资源) 需要在StorageClass对象中设置allowVolumeExpansion...storage.k8s.io/v1 kind: StorageClass metadata: name: nfs-client-storageclass provisioner: rookieops/nfs allowVolumeExpansion
storageclass设置allowVolumeExpansion: true: kind: StorageClass apiVersion: storage.k8s.io/v1 metadata:...userSecretNamespace: kube-system userSecretName: ceph-secret imageFormat: "2" imageFeatures: layering allowVolumeExpansion
kubectl get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
csi.storage.k8s.io/node-stage-secret-namespace: default csi.storage.k8s.io/fstype: ext4 reclaimPolicy: Delete allowVolumeExpansion...: true mountOptions: - discard clusterID对应之前的步骤中的fsid imageFeatures,这个是用来确定创建的image的特征的 allowVolumeExpansion...kubectl get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
apiVersion: storage.k8s.io/v1 metadata: name: longhorn provisioner: driver.longhorn.io allowVolumeExpansion
kubectl get sc 2 NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION
Standard_LRS provisioner: kubernetes.io/azure-disk reclaimPolicy: Delete volumeBindingMode: Immediate allowVolumeExpansion
"1" openstorage.io/auth-secret-name: px-k8s-user openstorage.io/auth-secret-namespace: portworx allowVolumeExpansion...controller-expand-secret-name: px-k8s-user csi.storage.k8s.io/controller-expand-secret-namespace: ${pvc.namespace} allowVolumeExpansion
领取专属 10元无门槛券
手把手带您无忧上云