You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The failure of "Expanding PVCs" in KinD clusters was first documented in #1716 . And at that time the Local Storage Provisioner "did not support volume expansion". However, shortly after it was discussed in rancher/local-path-provisioner#189, and afterwards the default storage class created for the provisioner had allowVolumeExpansion: true.
Since KinD creates its own storage class, instead of using the Helm Chart provided by the local-path-provisioner project, the storageClass must be updated here as well to support volume expansion. (Which the local path provisioner supports, because it doesn't actually place any limits on volume sizes in the first place)
The text was updated successfully, but these errors were encountered:
We currently ship this one but we would like to avoid excessively coupling to it.
Unfortunately these APIs can be somewhat tricky to support with a toy local driver and not actual volumes backed by a cloud provider, storage vendor, NFS, etc
There are some other local drivers in the kubernetes project we need to re-evaluate now, since the advent of CSI
The failure of "Expanding PVCs" in KinD clusters was first documented in #1716 . And at that time the Local Storage Provisioner "did not support volume expansion". However, shortly after it was discussed in rancher/local-path-provisioner#189, and afterwards the default storage class created for the provisioner had
allowVolumeExpansion: true
.Since KinD creates its own storage class, instead of using the Helm Chart provided by the local-path-provisioner project, the storageClass must be updated here as well to support volume expansion. (Which the local path provisioner supports, because it doesn't actually place any limits on volume sizes in the first place)
The text was updated successfully, but these errors were encountered: