Velero is unable to use an Azure storage account when deployed to AKS

Question

I'm deploying Velero using the CLI to deploy to an Azure AKS cluster with this command:

helm install velero vmware-tanzu/velero --namespace velero --set-file credentials.secretContents.cloud=./credentials-velero --set configuration.provider=azure --set configuration.backupStorageLocation.name=azure --set configuration.backupStorageLocation.bucket='velero' --set configuration.backupStorageLocation.config.resourceGroup=aks-testing-prod-003 --set configuration.backupStorageLocation.config.storageAccount=aks-testing-prod-003 --set snapshotsEnabled=true --set deployRestic=true --set configuration.volumeSnapshotLocation.name=azure --set image.repository=velero/velero --set image.pullPolicy=Always --set initContainers[0].name=velero-plugin-for-microsoft-azure --set initContainers[0].image=velero/velero-plugin-for-microsoft-azure:master --set initContainers[0].volumeMounts[0].mountPath=/target --set initContainers[0].volumeMounts[0].name=plugins

The pods come up just fine, velero and restic. But when I try to create a backup, it submits successfully but then fails with this error. Any help would be appreciated.

Name:         mybackup
Namespace:    velero
Labels:       velero.io/storage-location=azure
Annotations:  velero.io/source-cluster-k8s-gitversion=v1.19.11
              velero.io/source-cluster-k8s-major-version=1
              velero.io/source-cluster-k8s-minor-version=19

Phase:  Failed (run `velero backup logs mybackup` for more information)

Errors:    0
Warnings:  0

Namespaces:
  Included:  *
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        <none>
  Cluster-scoped:  auto

Label selector:  <none>

Storage Location:  azure

Velero-Native Snapshot PVs:  auto

TTL:  720h0m0s

Hooks:  <none>

Backup Format Version:  1.1.0

Started:    2021-06-10 16:32:58 +0000 UTC
Completed:  <n/a>

Expiration:  2021-07-10 16:32:58 +0000 UTC

Velero-Native Snapshots: <none included>

Answer 1

This issue is resolved?

We are facing the same issue from the velero pod's logs we can see a permission error to the storage bucket. Any help is greatly appreciated.

Answer 2

Hi Raju,

For AKS, i think the AZURE_RESOURCE_GROUP must point to the name of the auto-generated resource group that is created when you provision your AKS cluster in Azure, this is because your cluster's virtual machines/disks are in this resource group.