What happened:
There appears to not be any documentation on volume group specific parameters that could be passed in the VolumeGroupSnapshotClass. I have found that I can put any parameter I want in and it will be passed into the CreateVolumeGroupSnapshotRequest which works for my use case (e.g. to pass in storage device Secret and Namespace), however I would think there would be some standard parameter keys for passing in a secret name and namespace?
What you expected to happen:
I would expect some standard parameter keys for VolumeGroupSnapshotClass parameters specifically for secret name and namespace. I could not find documentation on this.
How to reproduce it:
Anything else we need to know?:
looking at the source code, I noticed that snapshot.storage.kubernetes.io/deletion-secret-name: or snapshot.storage.kubernetes.io/deletion-secret-namespace are looked for and passed to CreateVolumeGroupSnapshot requests if these parameters are specified in the VolumeGroupSnapshotClass .... These parameter key names seem confusing to me given they make their way into a CreateVolumeGroupSnapshot request, also the key name is not like the other key names in terms of naming convention.
What happened: There appears to not be any documentation on volume group specific parameters that could be passed in the VolumeGroupSnapshotClass. I have found that I can put any parameter I want in and it will be passed into the CreateVolumeGroupSnapshotRequest which works for my use case (e.g. to pass in storage device Secret and Namespace), however I would think there would be some standard parameter keys for passing in a secret name and namespace?
What you expected to happen:
I would expect some standard parameter keys for VolumeGroupSnapshotClass parameters specifically for secret name and namespace. I could not find documentation on this.
How to reproduce it:
Anything else we need to know?: looking at the source code, I noticed that snapshot.storage.kubernetes.io/deletion-secret-name: or snapshot.storage.kubernetes.io/deletion-secret-namespace are looked for and passed to CreateVolumeGroupSnapshot requests if these parameters are specified in the VolumeGroupSnapshotClass .... These parameter key names seem confusing to me given they make their way into a CreateVolumeGroupSnapshot request, also the key name is not like the other key names in terms of naming convention.
Environment:
kubectl version): 1.30.1uname -a):