I suspect the aws plugin not working with EKS auto-mode's ebs.csi.eks.amazonaws.com Provisioner

[nevotheless]

Hio Velero Community. I am currently trying getting a EBS Volume Snapshot Backup Running using my default Velero setup but i am getting a resource: /persistentvolumes name: /pvc-asdf message: /No volume ID returned by volume snapshotter for persistent volume. I haven't found anything useful in the velero pod logs and now i am suspecting the EKS Auto-Mode to be the pitfal here.

EKS Auto-Mode uses a different provisioner ebs.csi.eks.amazonaws.com instead of ebs.csi.aws.com and now i am wondering if the Velero plugin knows how to work with that.

Does someone know more about this or atleast how i could verify this being the case?
Would be going the csi snapshotter route a good alternative?

[kaovilai]

The plugin may not and need updating, but you should be able to use velero native csi functionality outside of the snapshotter plugin.

https://velero.io/docs/v1.17/csi/

Remove VSL, use velero CSI, and see if it works.

[kaovilai]

created #9254 to track plugin enhancement

[nevotheless]

Yeah this is what i was going to try tomorrow. I just need to add the external-snapshotter CRDs and Controller and it should just work i assume. The EKS Auto-Mode Docs unfortunately don't say anything about differences from ebs.csi.eks.amazonaws.com to ebs.csi.aws.com. Thanks for your input!