-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capacity value doesnot reflect in pvc list/status after updating storage request in PVC #746
Comments
this csi driver does not support resize |
Thanks @andyzhangx Can we add a feature where when we resize a PVC
I know there is not have a way to restrict the size of data inside a pv directory in nfs server. But atleast this will fix the issue of PVC size not reflecting correct status |
@navilg that's a dummy resize, it's better not doing that since this driver actually does not support resize. |
Even though it is a dummy resize it is really useful to be able to do that" resync in disk size" before backing up using Velero. This way the restore to another csi will create the right size pvc before restoring otherwise it just fails to restore. |
What happened:
I tried to edit a PVC and increase storage request, but it doesnot increase the storage size of PVC.
What you expected to happen:
I know since we are using NFS, It will use entire NFS volume and not restricted to PVC size, But atleast it should have updated the new capacity value in PV and in PVC for proper visual in PVC and PV list.
How to reproduce it:
resources.requests.storage
Anything else we need to know?:
is there a way as workaround to make sure PVC and PV size is reflected after we edit the storage request in PVC without making pod/app down.
Environment:
kubectl version
): 1.29uname -a
):The text was updated successfully, but these errors were encountered: