From 2ff23891e5ef7711266e045acf990d001b13f011 Mon Sep 17 00:00:00 2001 From: Jonny Ervine Date: Thu, 16 Nov 2023 20:26:32 +0800 Subject: [PATCH] Add plugins --- velero/values.home.yaml | 57 ++++++++++++++++++++--------------------- 1 file changed, 28 insertions(+), 29 deletions(-) diff --git a/velero/values.home.yaml b/velero/values.home.yaml index cda20c2..64bf17c 100644 --- a/velero/values.home.yaml +++ b/velero/values.home.yaml @@ -95,18 +95,18 @@ dnsPolicy: ClusterFirst # Init containers to add to the Velero deployment's pod spec. At least one plugin provider image is required. # If the value is a string then it is evaluated as a template. initContainers: - # - name: velero-plugin-for-csi - # image: velero/velero-plugin-for-csi:v0.6.0 - # imagePullPolicy: IfNotPresent - # volumeMounts: - # - mountPath: /target - # name: plugins - # - name: velero-plugin-for-aws - # image: velero/velero-plugin-for-aws:v1.8.0 - # imagePullPolicy: IfNotPresent - # volumeMounts: - # - mountPath: /target - # name: plugins + - name: velero-plugin-for-csi + image: velero/velero-plugin-for-csi:v0.6.0 + imagePullPolicy: IfNotPresent + volumeMounts: + - mountPath: /target + name: plugins + - name: velero-plugin-for-aws + image: velero/velero-plugin-for-aws:v1.8.0 + imagePullPolicy: IfNotPresent + volumeMounts: + - mountPath: /target + name: plugins # SecurityContext to use for the Velero deployment. Optional. # Set fsGroup for `AWS IAM Roles for Service Accounts` @@ -312,17 +312,17 @@ configuration: backupStorageLocation: # name is the name of the backup storage location where backups should be stored. If a name is not provided, # a backup storage location will be created with the name "default". Optional. - - name: + - name: minio # provider is the name for the backup storage location provider. - provider: + provider: aws # bucket is the name of the bucket to store backups in. Required. - bucket: + bucket: velero # caCert defines a base64 encoded CA bundle to use when verifying TLS connections to the provider. Optional. caCert: # prefix is the directory under which all Velero data should be stored within the bucket. Optional. - prefix: + prefix: home # default indicates this location is the default backup storage location. Optional. - default: + default: true # validationFrequency defines how frequently Velero should validate the object storage. Optional. validationFrequency: # accessMode determines if velero can write to this backup storage location. Optional. @@ -330,13 +330,13 @@ configuration: accessMode: ReadWrite credential: # name of the secret used by this backupStorageLocation. - name: + name: minio-creds # name of key that contains the secret data to be used. - key: + key: minio # Additional provider-specific configuration. See link above # for details of required/optional fields for your provider. - config: {} - # region: + config: + region: home-icarus # s3ForcePathStyle: # s3Url: # kmsKeyId: @@ -356,18 +356,18 @@ configuration: # See https://velero.io/docs/v1.6/api-types/volumesnapshotlocation/ volumeSnapshotLocation: # name is the name of the volume snapshot location where snapshots are being taken. Required. - - name: + - name: minio # provider is the name for the volume snapshot provider. - provider: + provider: aws credential: # name of the secret used by this volumeSnapshotLocation. - name: + name: minio-creds # name of key that contains the secret data to be used. - key: + key: minio # Additional provider-specific configuration. See link above # for details of required/optional fields for your provider. - config: {} - # region: + config: + region: home-icarus # apiTimeout: # resourceGroup: # The ID of the subscription where volume snapshots should be stored, if different from the cluster’s subscription. If specified, also requires `configuration.volumeSnapshotLocation.config.resourceGroup`to be set. (Azure only) @@ -473,7 +473,7 @@ credentials: name: # Name of a pre-existing secret (if any) in the Velero namespace # that should be used to get IAM account credentials. Optional. - existingSecret: + existingSecret: minio-creds # Data to be stored in the Velero secret, if `useSecret` is true and `existingSecret` is empty. # As of the current Velero release, Velero only uses one secret key/value at a time. # The key must be named `cloud`, and the value corresponds to the entire content of your IAM credentials file. @@ -514,7 +514,6 @@ nodeAgent: cpu: 500m memory: 512Mi limits: - cpu: 1000m memory: 1024Mi # Tolerations to use for the node-agent daemonset. Optional.