Improvement for k8s.io/docs/concepts/storage/volume-snapshot-classes/

[vinzent]

The docs say:

Administrators can specify a default VolumeSnapshotClass for VolumeSnapshots that don't request any particular class to bind to by adding the snapshot.storage.kubernetes.io/is-default-class: "true" annotation:

It does not mention, that the default annotation can be set by CSI driver and not only once for all VolumeSnapshotClass resources.

Relevant comments from issues regarding this matter:

It takes the PVC's driver from PVC storage class, and try to find any VolumeSnapshot class with the default annotation AND has the same driver PVC driver. If there are multiple matches or no match, the snapshot will fail.

kubernetes/kubernetes#94312 (comment)

and:

Confirmed this behaves as expected. Created two VolumeSnapshotClasses with different CSI drivers, both marked as default. Created a VolumeSnapshot without providing a volumeSnapshotClassName, and it used the correct VolumeSnapshotClass based on the provisioner of the PVC.

kubernetes/kubernetes#94312 (comment)

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dipesh-rawat]

Page reported in issue: https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes
/language en

[dipesh-rawat]

/sig storage