FileSystem per PVC - option

[dbones]

Is your feature request related to a problem?/Why is this needed A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I find having one FileSystemId per storage class is limiting

all the PVC's which are created have different reasons for life, with different backup policies, and different delete policies;

if we had to role back to a certain backup for one of the PVC's we would need to figure out how without impacting all other PVC's on the same FileSystem (even though they are in different PVCs, will be in the same filesystem, of which a backup is applied)

/feature

Describe the solution you'd like in detail A clear and concise description of what you want to happen.

a way to provide us to configure the FileSystem in the PVC, not storage class.

Storage class, when there is no FileSystemId provided

possible way:

provide a FileSystem Resource, allowing us to create a FileSystem in yaml

and the allowing us to reference the managed resource in a PVC

Another possible way:

PVC, will have an option to include the FileSystemId (annotation?)

• if provided, it creates an access point to the existing FileSystem
• if not provided, it create the filesystem, and access point <- default

the PVC will allow us to spec the folder/volume inside, default is /

it would be nice to be able to specify a back up policy as well against each PVC

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

• Crossplane (or an custom operator) to setup a storage class for every PVC (1 to 1)

Additional context Add any other context or screenshots about the feature request here.