values.yaml 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  1. # https://github.com/vmware-tanzu/helm-charts/blob/velero-11.4.0/charts/velero/values.yaml
  2. kubectl:
  3. image:
  4. repository: public.ecr.aws/bitnami/kubectl
  5. deployNodeAgent: true
  6. initContainers:
  7. - name: velero-plugin-for-aws
  8. image: velero/velero-plugin-for-aws:v1.13.1
  9. imagePullPolicy: IfNotPresent
  10. volumeMounts:
  11. - mountPath: /target
  12. name: plugins
  13. configuration:
  14. backupStorageLocation:
  15. - name: default
  16. provider: "velero.io/aws"
  17. bucket: "velero"
  18. default: true
  19. # validationFrequency defines how frequently Velero should validate the object storage. Optional.
  20. validationFrequency:
  21. # accessMode determines if velero can write to this backup storage location. Optional.
  22. # default to ReadWrite, ReadOnly is used during migrations and restores.
  23. accessMode: ReadWrite
  24. credential:
  25. # name of the secret used by this backupStorageLocation.
  26. name: velero-aws
  27. # name of key that contains the secret data to be used.
  28. key: credentials
  29. # Additional provider-specific configuration. See link above
  30. # for details of required/optional fields for your provider.
  31. config:
  32. s3Url: https://s3.bnuuy.org:8443
  33. region: default
  34. s3ForcePathStyle: "true"
  35. # kmsKeyId:
  36. # resourceGroup:
  37. # The ID of the subscription containing the storage account, if different from the cluster’s subscription. (Azure only)
  38. # subscriptionId:
  39. # storageAccount:
  40. # publicUrl:
  41. # Name of the GCP service account to use for this backup storage location. Specify the
  42. # service account here if you want to use workload identity instead of providing the key file.(GCP only)
  43. # serviceAccount:
  44. # Option to skip certificate validation or not if insecureSkipTLSVerify is set to be true, the client side should set the
  45. # flag. For Velero client Command like velero backup describe, velero backup logs needs to add the flag --insecure-skip-tls-verify
  46. # insecureSkipTLSVerify:
  47. # annotations allows adding arbitrary annotations to this BackupStorageLocation resource. Optional.
  48. annotations: {}
  49. ## Parameters for the VolumeSnapshotLocation(s). Configure multiple by adding other element(s) to the volumeSnapshotLocation slice.
  50. ## See https://velero.io/docs/v1.6/api-types/volumesnapshotlocation/
  51. volumeSnapshotLocation:
  52. - name: default
  53. provider: "velero.io/aws"
  54. credential:
  55. name: velero-aws
  56. key: credentials
  57. config:
  58. s3Url: https://s3.bnuuy.org:8443
  59. region: default
  60. s3ForcePathStyle: "true"
  61. defaultVolumesToFsBackup: false
  62. defaultItemOperationTimeout: 72h
  63. defaultBackupTTL: 144h
  64. features: EnableCSI
  65. schedules:
  66. default:
  67. disabled: false
  68. paused: false
  69. schedule: "0 2 * * *"
  70. useOwnerReferencesInBackup: false
  71. skipImmediately: false
  72. template:
  73. ttl: "240h"
  74. storageLocation: default
  75. includedNamespaces:
  76. - '*'