Chainguard Container for velero-plugin-for-microsoft-azure

Velero plugin for Microsoft Azure that provides backup and restore functionality for Azure Blob Storage and Azure Disk snapshots

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/velero-plugin-for-microsoft-azure:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The velero-plugin-for-microsoft-azure image is fully compatible with the public Velero plugin for Microsoft Azure. This image includes both the VolumeSnapshotter and ObjectStore plugins required for Azure integration:

• VolumeSnapshotter: Handles Azure Disk snapshots for persistent volume backups
• ObjectStore: Manages backups stored in Azure Blob Storage

The plugin is designed to be used as an init container with Velero deployments, following the standard Velero plugin architecture. There are no breaking changes from the public implementation.

Getting Started

The velero-plugin-for-microsoft-azure image is designed to be used as an init container in Velero deployments. The image contains a cp-plugin command that copies the plugin binary to a shared volume where Velero can load it.

Here's an example of using this image with a Velero deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: velero
  namespace: velero
spec:
  template:
    spec:
      serviceAccountName: velero
      initContainers:
      - name: velero-plugin-for-microsoft-azure
        image: cgr.dev/ORGANIZATION/velero-plugin-for-microsoft-azure:latest
        volumeMounts:
        - mountPath: /target
          name: plugins
      containers:
      - name: velero
        image: cgr.dev/ORGANIZATION/velero:latest
        command:
        - /velero
        args:
        - server
        - --plugin-dir=/plugins
        volumeMounts:
        - name: plugins
          mountPath: /plugins
      volumes:
      - name: plugins
        emptyDir: {}

When the init container runs, it will copy the plugin binary to /target/velero-plugin-for-microsoft-azure, making it available to the Velero server in the /plugins directory.

You can also install Velero with this plugin using the official Velero CLI:

velero install \
  --provider azure \
  --plugins cgr.dev/ORGANIZATION/velero-plugin-for-microsoft-azure:latest \
  --bucket my-backup-bucket \
  --secret-file ./credentials-velero

Configuration

To use this plugin, you'll need to configure Velero with Azure-specific settings. Create a BackupStorageLocation resource:

apiVersion: velero.io/v1
kind: BackupStorageLocation
metadata:
  name: azure
  namespace: velero
spec:
  provider: velero.io/azure
  objectStorage:
    bucket: my-backup-bucket
    prefix: velero-backups
  config:
    resourceGroup: my-resource-group
    storageAccount: mystorageaccount
    subscriptionId: 00000000-0000-0000-0000-000000000000

For Azure Disk snapshots, create a VolumeSnapshotLocation:

apiVersion: velero.io/v1
kind: VolumeSnapshotLocation
metadata:
  name: azure
  namespace: velero
spec:
  provider: velero.io/azure
  config:
    resourceGroup: my-resource-group
    subscriptionId: 00000000-0000-0000-0000-000000000000

You'll also need to provide Azure credentials to Velero. Create a secret with your Azure service principal credentials:

cat > credentials-velero <<EOF
AZURE_SUBSCRIPTION_ID=<your-subscription-id>
AZURE_TENANT_ID=<your-tenant-id>
AZURE_CLIENT_ID=<your-client-id>
AZURE_CLIENT_SECRET=<your-client-secret>
AZURE_RESOURCE_GROUP=<your-resource-group>
AZURE_CLOUD_NAME=AzurePublicCloud
EOF

kubectl create secret generic cloud-credentials \
  --namespace velero \
  --from-file cloud=credentials-velero

Documentation and Resources

• Velero plugin for Microsoft Azure documentation
• Velero supported providers documentation
• Azure Backup documentation

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.