From 8e43b4f8db71543a18d0e4ce5b3b61f2a404e5c1 Mon Sep 17 00:00:00 2001
From: paul david <423357+toothbrush@users.noreply.github.com>
Date: Wed, 14 Jun 2023 16:12:25 +1000
Subject: [PATCH 1/2] Default to empty volumeSnapshotLocation.

Without this default, i hit an error deploying Velero.

Signed-off-by: paul david <423357+toothbrush@users.noreply.github.com>
---
 charts/velero/values.yaml | 32 +++++++++++++++-----------------
 1 file changed, 15 insertions(+), 17 deletions(-)

diff --git a/charts/velero/values.yaml b/charts/velero/values.yaml
index 0a1806e4..18c1c750 100644
--- a/charts/velero/values.yaml
+++ b/charts/velero/values.yaml
@@ -276,24 +276,22 @@ configuration:
     #  flag. For Velero client Command like velero backup describe, velero backup logs needs to add the flag --insecure-skip-tls-verify
     #  insecureSkipTLSVerify:
 
-  # Parameters for the VolumeSnapshotLocation(s). Configure multiple by adding other element(s) to the volumeSnapshotLocation slice.
+  # Parameters for the VolumeSnapshotLocation(s). Configure multiple by adding element(s) to the volumeSnapshotLocation slice.
+  # Defaults to no volume snapshot locations (empty list).
   # 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:
-    # provider is the name for the volume snapshot provider.
-    provider:
-    # Additional provider-specific configuration. See link above
-    # for details of required/optional fields for your provider.
-    config: {}
-  #    region:
-  #    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)
-  #    subscriptionId:
-  #    incremental:
-  #    snapshotLocation:
-  #    project:
+  volumeSnapshotLocation: []
+    # Example:
+    # - name: foo
+    #   provider: aws
+    #   config:
+    #     region:
+    #     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)
+    #     subscriptionId:
+    #     incremental:
+    #     snapshotLocation:
+    #     project:
 
   # These are server-level settings passed as CLI flags to the `velero server` command. Velero
   # uses default values if they're not passed in, so they only need to be explicitly specified

From e718211448a741a555139fe96e08cd8f4a3a1378 Mon Sep 17 00:00:00 2001
From: paul david <423357+toothbrush@users.noreply.github.com>
Date: Wed, 14 Jun 2023 16:33:10 +1000
Subject: [PATCH 2/2] Bump chart version to 4.0.4

Signed-off-by: paul david <423357+toothbrush@users.noreply.github.com>
---
 charts/velero/Chart.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/charts/velero/Chart.yaml b/charts/velero/Chart.yaml
index 4724fef9..f9413432 100644
--- a/charts/velero/Chart.yaml
+++ b/charts/velero/Chart.yaml
@@ -3,7 +3,7 @@ appVersion: 1.11.0
 kubeVersion: ">=1.16.0-0"
 description: A Helm chart for velero
 name: velero
-version: 4.0.3
+version: 4.0.4
 home: https://github.com/vmware-tanzu/velero
 icon: https://cdn-images-1.medium.com/max/1600/1*-9mb3AKnKdcL_QD3CMnthQ.png
 sources: