Merge pull request vmware-tanzu#69 from jenting/v1.3.0

Bump velero version v1.3.0 and plugin version v1.0.1

charts/velero/Chart.yaml

@@ -1,8 +1,8 @@
 apiVersion: v1
-appVersion: 1.2.0
+appVersion: 1.3.0
 description: A Helm chart for velero
 name: velero
-version: 2.8.10
+version: 2.9.0
 home: https://github.com/vmware-tanzu/velero
 icon: https://cdn-images-1.medium.com/max/1600/1*-9mb3AKnKdcL_QD3CMnthQ.png
 sources:

charts/velero/README.md

@@ -6,11 +6,11 @@ Velero has two main components: a CLI, and a server-side Kubernetes deployment.
 
 ## Installing the Velero CLI
 
-See the different options for installing the [Velero CLI](https://velero.io/docs/v1.2.0/install-overview/#install-the-cli).
+See the different options for installing the [Velero CLI](https://velero.io/docs/v1.3.0/basic-install/#install-the-cli).
 
 ## Installing the Velero server
 
-This helm chart installs Velero version v1.2.0 https://github.com/vmware-tanzu/velero/tree/v1.2.0. See the [#Upgrading](#upgrading) section for information on how to upgrade from other versions.
+This helm chart installs Velero version v1.3.0 https://github.com/vmware-tanzu/velero/tree/v1.3.0. See the [#Upgrading](#upgrading) section for information on how to upgrade from other versions.
 
 ### Prerequisites
 
@@ -32,7 +32,7 @@ When installing using the Helm chart, the provider's credential information will
 
 The default configuration values for this chart are listed in values.yaml.
 
-See Velero's full [official documentation](https://velero.io/docs/v1.2.0/install-overview/). More specifically, find your provider in the Velero list of [supported providers](https://velero.io/docs/v1.2.0/supported-providers/) for specific configuration information and examples.
+See Velero's full [official documentation](https://velero.io/docs/v1.3.0/basic-install/). More specifically, find your provider in the Velero list of [supported providers](https://velero.io/docs/v1.3.0/supported-providers/) for specific configuration information and examples.
 
 #### Option 1) CLI commands
 
@@ -48,10 +48,10 @@ helm install --namespace <YOUR NAMESPACE> \
 --set configuration.volumeSnapshotLocation.name=<PROVIDER NAME> \
 --set configuration.volumeSnapshotLocation.config.region=<REGION> \
 --set image.repository=velero/velero \
---set image.tag=v1.2.0 \
+--set image.tag=v1.3.0 \
 --set image.pullPolicy=IfNotPresent \
 --set initContainers[0].name=velero-plugin-for-aws \
---set initContainers[0].image=velero/velero-plugin-for-aws:v1.0.0 \
+--set initContainers[0].image=velero/velero-plugin-for-aws:v1.0.1 \
 --set initContainers[0].volumeMounts[0].mountPath=/target \
 --set initContainers[0].volumeMounts[0].name=plugins \
 vmware-tanzu/velero
@@ -75,6 +75,10 @@ helm upgrade <RELEASE NAME> --set initContainers.backupStorageLocation.name=aws,
 
 ## Upgrading
 
+### Upgrading to v1.3.0
+
+The [instructions found here](https://velero.io/docs/v1.3.0/upgrade-to-1.3/) will assist you in upgrading from version v1.2.0 to v1.3.0.
+
 ### Upgrading to v1.2.0
 
 The [instructions found here](https://velero.io/docs/v1.2.0/upgrade-to-1.2/) will assist you in upgrading from version v1.0.0 or v1.1.0 to v1.2.0.

charts/velero/values.yaml

@@ -6,7 +6,7 @@
 # enabling restic). Required.
 image:
   repository: velero/velero
-  tag: v1.2.0
+  tag: v1.3.0
   pullPolicy: IfNotPresent
 
 # Annotations to add to the Velero deployment's pod template. Optional.
@@ -22,7 +22,7 @@ resources: {}
 # Init containers to add to the Velero deployment's pod spec. At least one plugin provider image is required.
 initContainers: []
   # - name: velero-plugin-for-aws
-  #   image: velero/velero-plugin-for-aws:v1.0.0
+  #   image: velero/velero-plugin-for-aws:v1.0.1
   #   imagePullPolicy: IfNotPresent
   #   volumeMounts:
   #     - mountPath: /target