Velero with Google Cloud Storage Buckets - Configure Velero

Customize Velero to allow the configuration of a non-default backup location.

Create a ConfigMap to allow Velero to use GCS buckets as backup storage location:

CODE

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ConfigMap
metadata:
  namespace: ${WORKSPACE_NAMESPACE}
  name: velero-overrides
data:
  values.yaml: |
    initContainers:
      - name: velero-plugin-for-gcp
        image: velero/velero-plugin-for-gcp:v1.5.0
        imagePullPolicy: IfNotPresent
        volumeMounts:
          - mountPath: /target
            name: plugins
    credentials:
      extraSecretRef: velero-gcp-credentials
EOF

Patch the Velero AppDeployment to reference the created ConfigMap with the Velero overrides:
1. To update Velero in all clusters in a workspace:
  CODE
```
cat << EOF | kubectl -n ${WORKSPACE_NAMESPACE} patch appdeployment velero --type="merge" --patch-file=/dev/stdin
spec:
  configOverrides:
    name: velero-overrides
EOF
```
2. To update Velero for a specific cluster in a workspace, see Customize an Application per Cluster.

Check the ConfigMap on the HelmRelease object:

CODE

kubectl get hr -n kommander velero -o jsonpath='{.spec.valuesFrom[?(@.name=="velero-overrides")]}'

The output looks like this if the deployment is successful:

CODE

{"kind":"ConfigMap","name":"velero-overrides"}

Ensure that the Velero pod is running:

CODE

kubectl get pods -A --kubeconfig=${CLUSTER_NAME}.conf |grep velero

You can also configure Velero by editing the kommander.yaml and rerunning the installation. To follow this alternative configuration path, expand the following section:

Alternative Configuration Path for Management/Essential Clusters

Configure Velero on the Management Cluster

Refresh the kommander.yaml to add the customization of Velero:
⚠ Before running this command, ensure the kommander.yaml is the configuration file you are currently using for your environment. Otherwise, your previous configuration will be lost. ⚠
CODE
```
dkp install kommander -o yaml --init > kommander.yaml
```

Configure DKP to load the plugins and to include the secret in the apps.velero section:
This process has been tested to work with plugin GCP v1.5.0. More recent versions of these plugins can be used, but have not been tested by D2iQ.

CODE

...
  velero:
    values: |
      initContainers:
        - name: velero-plugin-for-gcp
          image: velero/velero-plugin-for-gcp:v1.5.0
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - mountPath: /target
              name: plugins
      credentials:
        extraSecretRef: velero-gcp-credentials
...

Use the modified kommander.yaml configuration to install this Velero configuration:

CODE

dkp install kommander --installer-config kommander.yaml --kubeconfig=${CLUSTER_NAME}.conf

Check the ConfigMap on the HelmRelease object:

CODE

kubectl get hr -n kommander velero -o jsonpath='{.spec.valuesFrom[?(@.name=="velero-overrides")]}'

The output looks like this if the deployment is successful:

CODE

{"kind":"ConfigMap","name":"velero-overrides"}

Verify that the Velero pod is running:

CODE

kubectl get pods -A --kubeconfig=${CLUSTER_NAME}.conf |grep velero

Next Step:

Velero with Google Cloud Storage Buckets - Establish a Backup Location