vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
velero/examples
History
Steve Kriss a111eed2af update license headers to Velero contributors (#1302) 
Signed-off-by: Steve Kriss <krisss@vmware.com>
 		2019-03-20 12:32:48 -07:00
..
aws update license headers to Velero contributors (#1302) 2019-03-20 12:32:48 -07:00
azure update license headers to Velero contributors (#1302) 2019-03-20 12:32:48 -07:00
common update license headers to Velero contributors (#1302) 2019-03-20 12:32:48 -07:00
gcp update license headers to Velero contributors (#1302) 2019-03-20 12:32:48 -07:00
ibm update license headers to Velero contributors (#1302) 2019-03-20 12:32:48 -07:00
minio update license headers to Velero contributors (#1302) 2019-03-20 12:32:48 -07:00
nginx-app update license headers to Velero contributors (#1302) 2019-03-20 12:32:48 -07:00
README.md Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00

README.md

Examples

This directory contains sample YAML config files for running Velero on each core provider. Starting with v0.10, these files are packaged into the Velero release tarballs, and we highly recommend that you use the packaged versions of these files to ensure compatibility with the released code.

  • common/: Contains manifests to set up Velero. Can be used across cloud provider platforms. (Note that Azure requires its own deployment file due to its unique way of loading credentials).

  • minio/: Used in the Quickstart to set up Minio, a local S3-compatible object storage service. It provides a convenient way to test Velero without tying you to a specific cloud provider.

  • aws/, azure/, gcp/, ibm/: Contains manifests specific to the given cloud provider's setup.