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
Describe the problem/challenge you have
Currently, PVC sizes are applied using zfs quota field. This way, taking snapshot of a volume, decreases the available space of the PVC. I think this is not the desired behavior for many users.
Describe the solution you'd like
A simple solution is using refquota instead of quota.
A better solution is adding an option (operator-wide, per StorageClass or per PVC) to apply limits with refquota.
Another solution is provide a way (e.g. with annotations) to apply quota and refquota limits independently. For example, we can use the capacity property of PVC for refquota, and provide an annotation for limiting the zfs quota.
Environment:*
Not important
The text was updated successfully, but these errors were encountered:
I have one issue with #542: I think the CSI driver shouldn't be pinned to the quota/refquota choice it made at deploy time. It should be configurable via a storageClass parameter. Admins could choose if the provisioner uses quota/refquota at provision based on the StorageClass configuration.
I'm not a ZFS pro, but does the quota affect volume expansion?
Describe the problem/challenge you have
Currently, PVC sizes are applied using zfs
quota
field. This way, taking snapshot of a volume, decreases the available space of the PVC. I think this is not the desired behavior for many users.Describe the solution you'd like
A simple solution is using
refquota
instead ofquota
.A better solution is adding an option (operator-wide, per StorageClass or per PVC) to apply limits with
refquota
.Another solution is provide a way (e.g. with annotations) to apply
quota
andrefquota
limits independently. For example, we can use thecapacity
property of PVC forrefquota
, and provide an annotation for limiting the zfsquota
.Environment:*
The text was updated successfully, but these errors were encountered: