Skip to content

Latest commit

 

History

History
53 lines (45 loc) · 1.85 KB

volumesnapshotlocation.md

File metadata and controls

53 lines (45 loc) · 1.85 KB
Raw

Volume Snapshot Location

The following sample Azure VolumeSnapshotLocation YAML shows all of the configurable parameters. The items under spec.config can be provided as key-value pairs to the velero install command's --snapshot-location-config flag -- for example, apiTimeout=5m,resourceGroup=my-rg,....

apiVersion: velero.io/v1
kind: VolumeSnapshotLocation
metadata:
  name: azure-default
  namespace: velero
spec:
  # Name of the volume snapshotter plugin to use to connect to this location.
  #
  # Required.
  provider: velero.io/azure

  config:
    # How long to wait for an Azure API request to complete before timeout.
    #
    # Optional (defaults to 2m0s).
    apiTimeout: 5m

    # The name of the resource group where volume snapshots should be stored, if different
    # from the cluster's resource group.
    #
    # Optional.
    resourceGroup: my-rg

    # The ID of the subscription where volume snapshots should be stored, if different
    # from the cluster's subscription. Requires "resourceGroup" to also be set.
    #
    # Optional.
    subscriptionId: alt-subscription

    # URI of the AAD endpoint of the volume snapshots account.
    #
    # Note that the fully qualified AAD URI with http(s):// scheme is required to authenticate
    #
    # Optional. This will ensure that velero uses the provided AAD URI to authenticate to the volume snapshots account.
    activeDirectoryAuthorityURI: https://login.microsoftonline.us/

    # Azure offers the option to take full or incremental snapshots of managed disks.
    # - Set this parameter to true, to take incremental snapshots.
    # - If the parameter is omitted or set to false, full snapshots are taken (default).
    #
    # Optional.
    incremental: "<false|true>"

    # The tags added to the volume snapshots during the backup
    #
    # Optional.
    tags: key1=value1,key2=value2