There are mainly two categories of Velero plugins that can be specified while installing Velero:
-
defaultPlugins:
There are several types of default Velero plugins can be installed:AWSPlugins for AWSLegacy AWSPlugins for Legacy AWSGCPPlugins for Google Cloud PlatformAzurePlugins for Microsoft AzureOpenShiftOpenShift Velero PluginCSIPlugins for CSIkubevirtPlugins for Kubevirt
Note that only one of
AWSandLegacy AWSmay be installed at the same time.Legacy AWSis intended for use with certain S3 providers that do not support the V2 AWS SDK APIs used in theAWSplugin.For installation, you need to specify them in the
oadp_v1alpha1_dpa.yamlfile during deployment.apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: name: dpa-sample spec: configuration: velero: defaultPlugins: - openshift - aws - azure - gcpThe above specification will install Velero with four of the default plugins.
apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: name: dpa-sample spec: configuration: velero: defaultPlugins: - openshift - legacy-awsThe above specification will install Velero with two of the default plugins.
-
customPlugins:
For installation of custom Velero plugins, you need to specify the pluginimageand pluginnamein theoadp_v1alpha1_dpa.yamlfile during deployment.For instance,
apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: name: dpa-sample spec: configuration: velero: defaultPlugins: - azure - gcp customPlugins: - name: custom-plugin-example image: quay.io/example-repo/custom-velero-pluginThe above specification will install Velero with three plugins:
azure,gcp, andcustom-plugin-example.