You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
returnfalse, fmt.Errorf("%s and %s can not be both specified in DPA spec.configuration.velero.defaultPlugins", oadpv1alpha1.DefaultPluginAWS, oadpv1alpha1.DefaultPluginLegacyAWS)
-`GCP`[Plugins for Google Cloud Platform](https://github.com/vmware-tanzu/velero-plugin-for-gcp)
15
17
-`Azure`[Plugins for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure)
@@ -18,6 +20,8 @@ installing Velero:
18
20
-`kubevirt`[Plugins for Kubevirt](https://github.com/kubevirt/kubevirt-velero-plugin)
19
21
-`VSM (OADP 1.2 or below)`[Plugin for Volume-Snapshot-Mover](https://github.com/migtools/velero-plugin-for-vsm)
20
22
23
+
Note that only one of `AWS` and `Legacy AWS` may be installed at the same time. `Legacy AWS` is intended for use with certain S3 providers that do not support the V2 AWS SDK APIs used in the `AWS` plugin.
24
+
21
25
For installation,
22
26
you need to specify them in the `oadp_v1alpha1_dpa.yaml` file
23
27
during deployment.
@@ -37,7 +41,21 @@ installing Velero:
37
41
- gcp
38
42
```
39
43
The above specification will install Velero with four of the default plugins.
40
-
44
+
45
+
```
46
+
apiVersion: oadp.openshift.io/v1alpha1
47
+
kind: DataProtectionApplication
48
+
metadata:
49
+
name: dpa-sample
50
+
spec:
51
+
configuration:
52
+
velero:
53
+
defaultPlugins:
54
+
- openshift
55
+
- legacy-aws
56
+
```
57
+
The above specification will install Velero with two of the default plugins.
58
+
41
59
2.`customPlugins`:<br>
42
60
For installation of custom Velero plugins, you need to specify the plugin
43
61
`image` and plugin `name` in the `oadp_v1alpha1_dpa.yaml` file during
0 commit comments