enable/disable the snapshot auto delete flag on an ONTAP nfs flexvol
Describe the solution you'd like The ability to enable & disable the snapshot auto delete flag on an ONTAP nfs felxvol. This is to keep the user capacity as close as possible to the requested.
For example - PVC request is 100GiB, snapshot reserve is 10% container 'df' shows 90GiB If snapshot policy & user change rate is excessive snapshot reserve can exceed 10% - for example 40% then container 'df' shows 60GiB.
Being able to delete snapshots automatically would help alleviate this without the developers having to engage the storage team.
Describe alternatives you've considered Currently, if a developer creates a PV, there is no way to guarantee the "available" space other than:
Option 1:
1 – set “snapshot policy” to “none” 2 – set “snapshotReserve” to “0”
This disables snapshots and is against some organisational policies.
Option 2:
1 – make sure “spaceReserve” is “none” (thin provisioned) 2 – set “snapshotReserve” to 50% 3 – make PVC size double what user requested
Additional context Add any other context or screenshots about the feature request here.
We are running Trident in volumes that are protected with SVM-DR. Trident volumes are running out of space and this is impacting our replications. We are able to mitigate this problem by enabling the snapshot autodelete feature on the volumes, that´s a manual process. We would like to be able to provision the trident volumes with snap autodelete enabled by default.
FWIW, current releases of Trident add the snapshot reserve size to the Flexvols it provisions, so snapshots don't immediately begin consuming space requested in the PVC. Auto-deleting snapshots could leave Kubernetes VolumeSnapshotContent objects with no backing snapshot, which we'd prefer to avoid.