You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I create a VolumeSnapshot, the corresponding DO snapshot created by the CSI is given a name like snapshot-8fb09ea8-d2af-465f-9a84-e121351aaf5b, with the prefix snapshot- followed by a UUID. This makes it hard to understand what a snapshot contains, and which is the corresponding kubernetes VolumeSnapshot.
I'd like to be able to somehow specify the name of the underlying snapshot created by the CSI. This would allow me to give meaningful names to the snapshots, so that I can identify these more easily.
For example, one way of doing this could be using annotations on the VolumeSnapshot metadata:
When I create a VolumeSnapshot, the corresponding DO snapshot created by the CSI is given a name like
snapshot-8fb09ea8-d2af-465f-9a84-e121351aaf5b
, with the prefixsnapshot-
followed by a UUID. This makes it hard to understand what a snapshot contains, and which is the corresponding kubernetes VolumeSnapshot.I'd like to be able to somehow specify the name of the underlying snapshot created by the CSI. This would allow me to give meaningful names to the snapshots, so that I can identify these more easily.
For example, one way of doing this could be using annotations on the VolumeSnapshot metadata:
This would instruct the CSI to use
db-snapshot-1
as the name for the result DigitalOcean snapshot.The text was updated successfully, but these errors were encountered: