velero/examples
Nolan Brubaker 43714caaec Rename Ark to Velero!!!
Signed-off-by: Nolan Brubaker <brubakern@vmware.com>
2019-02-04 17:35:22 -05:00
..
aws Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
azure Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
common Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
gcp Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
ibm Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
minio Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
nginx-app Rename Ark to Velero!!! 2019-02-04 17:35:22 -05: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.