Skip to content

Commit c0c4564

Browse files
update VolumeSnapshotClass
1 parent db301d5 commit c0c4564

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

content/en/docs/concepts/storage/volume-snapshot-classes.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,6 +67,22 @@ deletionPolicy: Delete
6767
parameters:
6868
```
6969

70+
If multiple CSI drivers exist, a default VolumeSnapshotClass can be specified
71+
for each of them.
72+
73+
### VolumeSnapshotClass dependencies
74+
75+
When you create a VolumeSnapshot without specifying a VolumeSnapshotClass, Kubernetes
76+
automatically selects a default VolumeSnapshotClass that has a CSI driver matching
77+
the CSI driver of the PVC’s StorageClass.
78+
79+
This behavior allows multiple default VolumeSnapshotClass objects to coexist in a cluster, as long as
80+
each one is associated with a unique CSI driver.
81+
82+
Always ensure that there is only one default VolumeSnapshotClass for each CSI driver. If
83+
multiple default VolumeSnapshotClass objects are created using the same CSI driver,
84+
a VolumeSnapshot creation will fail because Kubernetes cannot determine which one to use.
85+
7086
### Driver
7187

7288
Volume snapshot classes have a driver that determines what CSI volume plugin is

0 commit comments

Comments
 (0)