Closed Ruakij closed 1 month ago
I encountered the same issue. Do we have a solution here?
I encountered the same issue. Do we have a solution here?
Well you can create a new PV (or let one create from PVC) and rename the old folder in /buckets to the new one. (e.g. via filer) I think thats all you can really do to solve this at the moment.
The best solution is not to transfer capacity through volumeAttributes, but to obtain capacity from the k8s API through volumeID; Otherwise, after the container is remounted, the capacity before expansion will be restored.
I will submit a PR to fix this issue later.
@chrislusf This issue can be closed now
I had created a volume via PVC too small. So i increased its size and made sure the Resizer changed everything.
Both, the PVC and PV now have the correct
spec.capacity.storage
, but the PV didnt have its fieldspec.csi.volumeAttributes.volumeCapacity
updated. This field is used by the driver to set the quota, so the resize effectively only worked on paper, but the mount has the same virtual limit set.The resizer claims the resize was a success.
Steps to reproduce:
spec.csi.volumeAttributes.volumeCapacity
on old value.