From a63a82fcb07d435c0dd56bb0cddc8b0c22e94675 Mon Sep 17 00:00:00 2001 From: Ashish Amarnath Date: Wed, 22 Jul 2020 11:49:47 -0700 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=96=20update=20csi=20docs=20to=20docum?= =?UTF-8?q?ent=20volumesnapshotclass=20label=20(#2741)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Ashish Amarnath --- site/docs/main/csi.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/site/docs/main/csi.md b/site/docs/main/csi.md index 2e7c06cce..e91286b08 100644 --- a/site/docs/main/csi.md +++ b/site/docs/main/csi.md @@ -37,10 +37,10 @@ This section documents some of the choices made during implementation of the Vel 1. Volumesnapshots created by the plugin will be retained only for the lifetime of the backup even if the `DeletionPolicy` on the volumesnapshotclass is set to `Retain`. To accomplish this, during deletion of the backup the prior to deleting the volumesnapshot, volumesnapshotcontent object will be patched to set its `DeletionPolicy` to `Delete`. Thus deleting volumesnapshot object will result in cascade delete of the volumesnapshotcontent and the snapshot in the storage provider. 1. Volumesnapshotcontent objects created during a velero backup that are dangling, unbound to a volumesnapshot object, will also be discovered, through labels, and deleted on backup deletion. - -# Known Limitations - -1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/vmware-tanzu/velero-plugin-for-csi/issues/17)_ +1. The Velero CSI plugin, to backup CSI backed PVCs, will choose the VolumeSnapshotClass in the cluster that has the same driver name and also has the `velero.io/csi-volumesnapshot-class` label set on it, like +```yaml +velero.io/csi-volumesnapshot-class: "true" +``` # Roadmap