This is the documentation for the latest development version of Velero. Both code and docs may be unstable, and these docs are not guaranteed to be up to date or correct. See the latest version.
Velero supports a variety of storage providers for different backup and snapshot operations. Velero has a plugin system which allows anyone to add compatibility for additional backup and volume storage platforms without modifying the Velero codebase.
|AWS S3||Velero Team||Slack, GitHub Issue|
|Azure Blob Storage||Velero Team||Slack, GitHub Issue|
|Google Cloud Storage||Velero Team||Slack, GitHub Issue|
Velero uses Amazon’s Go SDK to connect to the S3 API. Some third-party storage providers also support the S3 API, and users have reported the following providers work with Velero:
Note that these providers are not regularly tested by the Velero team.
Some storage providers, like Quobyte, may need a different signature algorithm version.
|AWS EBS||Velero Team||Slack, GitHub Issue|
|Azure Managed Disks||Velero Team||Slack, GitHub Issue|
|Google Compute Engine Disks||Velero Team||Slack, GitHub Issue|
|Restic||Velero Team||Slack, GitHub Issue|
|Portworx||Portworx||Slack, GitHub Issue|
To write a plugin for a new backup or volume storage system, take a look at the example repo.
After you publish your plugin, open a PR that adds your plugin to the appropriate list.