Upgrade e2e tests to new plugin versions (v1.2)

Signed-off-by: Carlisia <carlisia@vmware.com>

site/content/docs/main/release-instructions.md

@@ -100,7 +100,9 @@ These are the steps to update the Velero Homebrew version.
 -
 ### Plugins
 
-To release plugins maintained by the core team, follow the [plugin release instructions](plugin-release-instructions.md).
+To release plugins maintained by the Velero team, follow the [plugin release instructions](plugin-release-instructions.md).
+
+After the plugin images are built, be sure to update any [e2e tests][3] that use these plugins.
 
 ## How to write and release a blog post
 What to include in a release blog:
@@ -130,3 +132,4 @@ What to include:
 
 [1]: https://velero.io/blog
 [2]: website-guidelines.md
+[3]: test/e2e/velero_utils.go

test/e2e/velero_utils.go

@@ -28,11 +28,11 @@ func getProviderPlugins(providerName string) []string {
 	// TODO: make plugin images configurable
 	switch providerName {
 	case "aws":
-		return []string{"velero/velero-plugin-for-aws:v1.1.0"}
+		return []string{"velero/velero-plugin-for-aws:v1.2.0"}
 	case "azure":
-		return []string{"velero/velero-plugin-for-microsoft-azure:v1.1.2"}
+		return []string{"velero/velero-plugin-for-microsoft-azure:v1.2.0"}
 	case "vsphere":
-		return []string{"velero/velero-plugin-for-aws:v1.1.0", "velero/velero-plugin-for-vsphere:v1.1.0"}
+		return []string{"velero/velero-plugin-for-aws:v1.2.0", "velero/velero-plugin-for-vsphere:v1.1.0"}
 	default:
 		return []string{""}
 	}