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:AWS
Plugins for AWSLegacy AWS
Plugins for Legacy AWSGCP
Plugins for Google Cloud PlatformAzure
Plugins for Microsoft AzureOpenShift
OpenShift Velero PluginCSI
Plugins for CSIkubevirt
Plugins for KubevirtVSM (OADP 1.2 or below)
Plugin for Volume-Snapshot-Mover
Note that only one of
AWS
andLegacy 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 theAWS
plugin.For installation, you need to specify them in the
oadp_v1alpha1_dpa.yaml
file during deployment.apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: name: dpa-sample spec: configuration: velero: defaultPlugins: - openshift - aws - azure - gcp
The 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-aws
The above specification will install Velero with two of the default plugins.
-
customPlugins
:
For installation of custom Velero plugins, you need to specify the pluginimage
and pluginname
in theoadp_v1alpha1_dpa.yaml
file 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-plugin
The above specification will install Velero with three plugins:
azure
,gcp
, andcustom-plugin-example
.