VolumeSnapshots: Missing Limitations for VolumeClasses if those don't support snapshots

[Maximilian-Pfau-P]

e.g. nas-economy doesn't provide snapshot functionality, but those PVC's can be selected for snapshots which results in errors.

level=error msg="GRPC error: rpc error: code = FailedPrecondition desc = snapshots are not supported by backend type ontap-nas-economy" requestID=5f1be14f-4ae3-4317-a2fa-b0a7cace57b8 requestSource=CSI

There should be some configuration options for admins to limit the storage classes for which snapshots can be created, otherwise user-errors can't be reliably prevented.

trident: 20.07

[balaramesh]

@maxger while this could be achieved with Trident, I am not sure if it will help solve the issue itself. It would change where the error is reported. This error that you see would also be observed on the VolumeSnapshot object when you do a kubectl describe.

[Maximilian-Pfau-P]

@balaramesh

Ok, thank for the response.

I know where I would find the errors, I just have the conviction that we should‘nt enable users to create new objects which don‘t work.

So I have to block the snapshot feature which I find really unfortunate.
I just hoped that I have overlooked a option.

Best Regards,
Max