deploy-templates/charts/velero/ci/test-values.yaml (75 lines of code) (raw):
# Set provider name and backup storage location bucket name
configuration:
provider: aws
backupStorageLocation:
name: primary
bucket: velero
default: true
config:
region: us-west-1
profile: test
volumeSnapshotLocation:
provider: aws
config:
bucket: velero
region: us-west-1
schedules:
mybackup:
labels:
myenv: foo
schedule: "0 0 * * *"
template:
ttl: "240h"
includedNamespaces:
- foo
# Set a service account so that the CRD clean up job has proper permissions to delete CRDs
serviceAccount:
server:
name: velero
# The Velero server
# Annotations to Velero deployment
annotations:
annotation: velero
foo: bar
# Labels to Velero deployment
labels:
label: velero
foo: bar
# Annotations to Velero deployment's template
podAnnotations:
pod-annotation: velero
foo: bar
# Labels to Velero deployment's template
podLabels:
pod-label: velero
foo: bar
# Resources to Velero deployment
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 100m
memory: 128Mi
# The restic daemonset
deployRestic: true
restic:
# Annotations to restic daemonset
annotations:
annotation: restic
foo: bar
# Labels to restic daemonset
labels:
label: restic
foo: bar
# Resources to restic daemonset
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 100m
memory: 128Mi
# The kubectl upgrade/cleanup job
kubectl:
# Annotations to kubectl job
annotations:
annotation: kubectl
foo: bar
# Labels to kubectl job
labels:
label: kubectl
foo: bar
# Resources to kubectl job
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 100m
memory: 128Mi
# Whether or not to clean up CustomResourceDefintions when deleting a release.
# Cleaning up CRDs will delete the BackupStorageLocation and VolumeSnapshotLocation instances, which would have to be reconfigured.
# Backup data in object storage will _not_ be deleted, however Backup instances in the Kubernetes API will.
# Always clean up CRDs in CI.
cleanUpCRDs: true