This directory contains common velero resources, schedules.
This directory does not provide any functionality by itself. Please refer to the different Velero deployment options:
These deployments can use this base to deploy pre-configure velero schedules.
The full
backup Schedule requires to have defined:
default
VolumeSnapshotLocation in thekube-system
namespace.
The manifest
backup Schedule requires to have defined:
default
BackupStorageLocation in thekube-system
namespace.
As this base creates a Schedule
it's required to have a VolumeSnapshotLocation
named default
to automate the full backup creation.
This module provides a set of terraform modules (aws, gcp and azure) that creates it as terraform output:
Example GCP VolumeSnapshotLocation
$ terraform init
$ terraform apply
$ terraform output -raw volume_snapshot_location > /tmp/volume_snapshot_location.yaml
$ cat /tmp/volume_snapshot_location.yaml
apiVersion: velero.io/v1
kind: VolumeSnapshotLocation
metadata:
name: default
spec:
provider: velero.io/gcp
Then you are ready to apply this file in the kube-system
namespace:
$ kubectl apply -f /tmp/volume_snapshot_location.yaml -n kube-system
# omitted output
As this base creates a Schedule
it's required to have a BackupStorageLocation
named default
to automate the manifests backup creation.
This module provides a set of terraform modules (aws, gcp and azure) that creates it as terraform output:
Example GCP BackupStorageLocation
$ terraform init
# omitted output
$ terraform apply
# omitted output
$ terraform output -raw backup_storage_location > /tmp/backup_storage_location.yaml
# omitted output
$ cat /tmp/backup_storage_location.yaml
apiVersion: velero.io/v1
kind: BackupStorageLocation
metadata:
name: default
spec:
provider: velero.io/gcp
objectStorage:
bucket: my-gcs-velero-bucket
prefix: velero
Then you are ready to apply this file in the kube-system
namespace:
$ kubectl apply -f /tmp/backup_storage_location.yaml -n kube-system
# omitted output
If you choose to deploy the velero on prem package, this resource is preconfigured in the cluster.
For license details please see LICENSE