NFS PVC resizing

[restive shuttle]

We are looking to adopt a new storage policy for our pcv volumes to update the -percent-snapshot-space snapshotreserve from 5% to 50%. We have some volumes with 100% snapshot reserve and like to avoid the snapshot overflow. Is this ok to adjust from the ontap side? I wasn't sure if the open shift/trident resize was the equivalent of:
Vol modify -size 2g
Or
Vol modify -size +1g

Does anyone have best practices of findings around this behavior to share?

For new volumes we have snapshotreserve set to 50 in the storage policy yaml file, but would like to correct all of the existing PVC volumes to match

[exotic spire]

Hi @restive shuttle , you just have to use the CSI online volume expansion that comes with Trident. Trident will expand the volume in ONTAP. In this way, the size of the volume is kept aligned and the same between ONTAP and Kubernetes. If you do it in ONTAP, Kubernetes is not aware of the new size of the volume. Just edit/patch the PVC and in spec: resources: request: storage: put the new desired size, for example 2Gi

[restive shuttle]

Thanks. I will do some testing with our kubernettes team next week. We hope to adjust snapshotreserve but keep the data side of the volume the same. Our concern was the kubernettes would not know he new volume size for the next resize.