mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-07 13:55:20 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Files
e4c05f2ddfeb6906e1ff4019c68f0fc57a883139
velero/site/content/docs/v1.3.2/csi.md
Tony Batard c663ce15ab Hugo migration (#2720) 
* Move files to a Hugo structure

Signed-off-by: Tony Batard <tbatard@pivotal.io>
2020-08-13 09:09:15 -07:00

2.4 KiB
Raw Blame History

title, layout
title layout
Container Storage Interface Snapshot Support in Velero docs

This feature is under development. Documentation may not be up-to-date and features may not work as expected.

Prerequisites

The following are the prerequisites for using Velero to take Container Storage Interface (CSI) snapshots:

  1. The cluster is Kubernetes version 1.17 or greater.
  2. The cluster is running a CSI driver capable of support volume snapshots at the v1beta1 API level.
  3. The Velero server is running with the --features EnableCSI feature flag to enable CSI logic in Velero's core.
  4. The Velero CSI plugin is installed to integrate with the CSI volume snapshot APIs.
  5. When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster is the same as that on the source cluster to ensure cross cluster portability of CSI volumesnapshots

Implementation Choices

This section documents some of the choices made during implementation of the Velero CSI plugin:

  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.
  2. 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, to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. Issue #17

Roadmap

Velero's support level for CSI volume snapshotting will follow upstream Kubernetes support for it, and will reach general availability sometime after volume snapshotting is GA in upstream Kubernetes. Beta support is expected to launch in Velero v1.4.