kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #49381 from network-charles/network-charles-patch-4 

Update the Volume Snapshot Classes Page
pull/49383/head
Kubernetes Prow Robot 2025-01-09 14:30:30 -08:00 committed by GitHub
parent e58bb8adf2 c0c456446e
commit d723e0b8c5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -67,6 +67,22 @@ deletionPolicy: Delete
parameters:
```
If multiple CSI drivers exist, a default VolumeSnapshotClass can be specified
for each of them.
### VolumeSnapshotClass dependencies
When you create a VolumeSnapshot without specifying a VolumeSnapshotClass, Kubernetes
automatically selects a default VolumeSnapshotClass that has a CSI driver matching
the CSI driver of the PVC’s StorageClass.
This behavior allows multiple default VolumeSnapshotClass objects to coexist in a cluster, as long as
each one is associated with a unique CSI driver.
Always ensure that there is only one default VolumeSnapshotClass for each CSI driver. If
multiple default VolumeSnapshotClass objects are created using the same CSI driver,
a VolumeSnapshot creation will fail because Kubernetes cannot determine which one to use.
### Driver
Volume snapshot classes have a driver that determines what CSI volume plugin is