Yuji Ito

Originally, the minimum allocation size was 1 GiB. Therefore, I do not object to setting a new minimum allocation. However, we may avoid hard-coding these numbers. Some sites may not...

> I am open to ideas here. I would like to keep the configuration ability to configure not only flat limits, but also per VolumeMode/Type for specific Filesystems. It seems...

I found a little problem when using the StorageClass to set new configurations: we cannot edit the existing SC. we have to recreate the SC with the same name for...

> using minimum-allocated-size-filesystem and minimum-allocated-size-block because the same storageclass might be used for both VolumeMode Filesystem and Block but the user might only want to limit Filesystem Volumes, not block...

@jakobmoellerdev The use of storage class may be excessive for this issue. I suppose using the controller's arguments might be better than using SC to resolve the original issue. I...

Thank you for your reply. > Would it be okay for you to create 2 flags for the controller configuration? How about specifying the minimum allocation size per xfs/ext4/btrfs/block using...

I think using ConfigMap and DeviceClass are overdoing for this issue. Wouldn't it be better to specify the minimum allocated size by the controller's argument this time? When there are...

Could you tell me what custom tuned filesystem and block device settings are? Does this mean the small sized fses/bdevs like < 1GiB? IMO, the minimum allocation size is not...

@jakobmoellerdev We are discussing this internally and going to get back to you tomorrow.

> Sure: We have 2 different use cases for the differentiation by device Class: > 1. Customers want to use LVM Block Partitions for VM bootstrapping and want to use...