Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Velero Backup not working for Azure AKS #598

Open
faizanbashir opened this issue Jul 8, 2024 · 0 comments
Open

Velero Backup not working for Azure AKS #598

faizanbashir opened this issue Jul 8, 2024 · 0 comments

Comments

@faizanbashir
Copy link

What steps did you take and what happened:
I am trying to install Velero to take backups for our AKS cluster, but it is failing with the errors. I have created a Storage account container to store the backups from velero.

Installation Command:

helm upgrade --install \
    velero \
    vmware-tanzu/velero \
    --namespace velero \
    --create-namespace \
    --set-file credentials.secretContents.cloud=velerobackup \
    --set fullnameOverride=velero \
    --set image.repository=docker.io/velero/velero \
    --set "configuration.backupStorageLocation[0].config.region=eastus" \
    --set "configuration.backupStorageLocation[0].bucket=akspsrusclusterbacup" \
    --set "configuration.backupStorageLocation[0].provider=Azure" \
    --set "configuration.backupStorageLocation[0].config.storageAccount=akspsrusclusterbacup" \
    --set "configuration.backupStorageLocation[0].config.storageAccountURI=https://akspsrusclusterbacup.blob.core.windows.net \
    --set "configuration.backupStorageLocation[0].config.storageAccountKeyEnvVar=" \
    --set "initContainers[0].name=velero-plugin-for-azure" \
    --set "initContainers[0].image=docker.io/velero/velero-plugin-for-microsoft-azure:v1.9.2" \
    --set "initContainers[0].volumeMounts[0].mountPath=/target" \
    --set "initContainers[0].volumeMounts[0].name=plugins" \
    --set snapshotsEnabled=false \
    --set credentials.useSecret=true \
    --set kubectl.image.repository=docker.io/bitnami/kubectl \
    --values schedules.yaml

What did you expect to happen:
The velero backup should work and write the backups to the storage account container designated for it.

The output of the following commands will help us better understand what's going on:

time="2024-07-08T06:41:41Z" level=error msg="Error getting backup store for this location" backupLocation=velero/default controller=backup-sync error="unable to locate ObjectStore plugin named velero.io/Azure" logSource="pkg/controller/backup_sync_controller.go:101"
time="2024-07-08T06:41:41Z" level=error msg="Error getting a backup store" backup-storage-location=velero/default controller=backup-storage-location error="unable to locate ObjectStore plugin named velero.io/Azure" logSource="pkg/controller/backup_storage_location_controller.go:137"
time="2024-07-08T06:41:41Z" level=info msg="BackupStorageLocation is invalid, marking as unavailable" backup-storage-location=velero/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:120"
time="2024-07-08T06:41:41Z" level=error msg="Current BackupStorageLocations available/unavailable/unknown: 0/1/0, BackupStorageLocation \"default\" is unavailable: unable to locate ObjectStore plugin named velero.io/Azure)" controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:178"
time="2024-07-08T06:42:41Z" level=error msg="Error getting backup store for this location" backupLocation=velero/default controller=backup-sync error="unable to locate ObjectStore plugin named velero.io/Azure" logSource="pkg/controller/backup_sync_controller.go:101"
time="2024-07-08T06:42:41Z" level=error msg="Error getting a backup store" backup-storage-location=velero/default controller=backup-storage-location error="unable to locate ObjectStore plugin named velero.io/Azure" logSource="pkg/controller/backup_storage_location_controller.go:137"
time="2024-07-08T06:42:41Z" level=info msg="BackupStorageLocation is invalid, marking as unavailable" backup-storage-location=velero/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:120"
time="2024-07-08T06:42:41Z" level=error msg="Current BackupStorageLocations available/unavailable/unknown: 0/1/0, BackupStorageLocation \"default\" is unavailable: unable to locate ObjectStore plugin named velero.io/Azure)" controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:178"
time="2024-07-08T06:43:41Z" level=error msg="Error getting backup store for this location" backupLocation=velero/default controller=backup-sync error="unable to locate ObjectStore plugin named velero.io/Azure" logSource="pkg/controller/backup_sync_controller.go:101"
time="2024-07-08T06:43:41Z" level=error msg="Error getting a backup store" backup-storage-location=velero/default controller=backup-storage-location error="unable to locate ObjectStore plugin named velero.io/Azure" logSource="pkg/controller/backup_storage_location_controller.go:137"
time="2024-07-08T06:43:41Z" level=info msg="BackupStorageLocation is invalid, marking as unavailable" backup-storage-location=velero/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:120"
time="2024-07-08T06:43:41Z" level=error msg="Current BackupStorageLocations available/unavailable/unknown: 0/1/0, BackupStorageLocation \"default\" is unavailable: unable to locate ObjectStore plugin named velero.io/Azure)" controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:178"

Environment:

  • helm version (use helm version): v3.14.2
  • helm chart version and app version (use helm list -n <YOUR NAMESPACE>): 1.14.0
  • Kubernetes version (use kubectl version): 1.28.9
  • Kubernetes installer & version: -
  • Cloud provider or hardware configuration: Azure AKS
  • OS (e.g. from /etc/os-release): -
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant