Open D1StrX opened 1 month ago
Hi @D1StrX, there is no way to get the sigs k8s library that we use to support resize. You might want to follow this doc if you're using XFS/EXT4 quota: https://github.com/openebs/dynamic-localpv-provisioner/blob/develop/docs/tutorials/hostpath/xfs_quota/modify-xfs-quota.md
Ref: https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/issues/43
If you're not using filesystem quota, the PV doesn't really limit your workloads to the PVC's 'capacity' value. The only limitation to your workloads would be the capacity of the filesystem. You'd not need to change the PVC size to be able to write beyond the storage capacity.
Good to know. Not using quotas 👌
Describe the problem/challenge you have While having a new storageClass with
AllowVolumeExpansion: True
, a storage size change of a PVC for a deployment isn't changing the size. Describing the PVC says it has the new spec, butWarning ExternalExpanding 14m volume_expand waiting for an external controller to expand this PVC
Describe the solution you'd like Allow volume expanding with dynamic-localpv-provisioner.
Environment:
kubectl get po -n openebs --show-labels
): 4.1.1kubectl version
): 1.30cat /etc/os-release
): Ubuntu 22.04