Is your feature request related to a problem?/Why is this needed
FSx Lustre filesystems are large (minimum 1.2T). As a result, it would be nice to be able to couple related applications within a particular FSx Lustre filesystem.
/feature
Describe the solution you'd like in detail
For instance:
- Create a StorageClass that targets an existing / static FSx Lustre filesystem
- When a PVC is requested against that storage class, a directory is created within the root of the system
- The PVC is filled / bound to this directory and made available to the application
- As a result, several applications have mutually exclusive access to a subdirectory of the FSx Lustre filesystem
Describe alternatives you've considered
- Independent FSx Lustre filesystem per application (cost prohibitive)
- Use several PVs (one per application) to target the same filesystem at different
mountnames (mount sub-paths)
- Select the corresponding PV with the application's PVC
- Less than ideal because requires a PV per application
- Also requires the subdirectories to be created manually within the FSx Lustre filesystem (or the mount / PVC binding will not succeed)
Additional context
This feature is prompted by the nfs-subdir-external-provisioner's behavior (although nfs-server-provisioner works much the same way too).
Is your feature request related to a problem?/Why is this needed
FSx Lustre filesystems are large (minimum 1.2T). As a result, it would be nice to be able to couple related applications within a particular FSx Lustre filesystem.
/feature
Describe the solution you'd like in detail
For instance:
Describe alternatives you've considered
mountnames (mount sub-paths)Additional context
This feature is prompted by the
nfs-subdir-external-provisioner's behavior (although nfs-server-provisioner works much the same way too).