-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
Not Selected
-
ToDo
-
-
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
None
This issue tracks the upstream Velero GitHub issue #9033 which is part of the Velero v1.18 milestone.
Description
There is already some discussion about this topic in PR #8946. This issue will continue to focus on this topic to check whether it's possible to not include the VolumeSnapshotClass in the CSI backup and restore process.
The VolumeSnapshotClassName is an optional parameter for VolumeSnapshotSpec, and according to the external-snapshotter document: If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used.
From external-snapshotter code, even if the controller fails to find the VolumeSnapshotClass for the VolumeSnapshot, it will also treat the VolumeSnapshot as pre-provisioned.
As a result, in theory, the CSI backup and restore process should not require the VolumeSnapshotClass to work.
Upstream Details
- GitHub Issue: https://github.com/vmware-tanzu/velero/issues/9033
- Status: Open
- Assignee: blackpiglet
- Labels: backlog
- Created: 2025-06-20T07:17:51Z
- Updated: 2025-09-17T06:07:39Z
The goal is to test and verify the CSI B/R can work without VolumeSnapshotClass.