velero-plugin-for-microsoft-azure | Plugins to support Velero on Microsoft Azure | Azure library
kandi X-RAY | velero-plugin-for-microsoft-azure Summary
kandi X-RAY | velero-plugin-for-microsoft-azure Summary
This repository contains these plugins to support running Velero on Microsoft Azure:.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- getStorageAccountKey retrieves the storage account key from the configuration .
- getSnapshotTags merges the tags into a snapshot
- parseFullSnapshotName extracts the full snapshot identifier
- getBlockSize returns the block size from the config
- getRequiredValues returns a map of required values
- selectCredentialsFile retrieves the credentials file from the config .
- GetVolumeInfo returns the name of the given volume .
- loadCredentialsIntoEnv loads credentials into godotenv
- parseAzureEnvironment returns azure . Environment from CloudName
- getSubscriptionID returns the subscription ID from the configuration
velero-plugin-for-microsoft-azure Key Features
velero-plugin-for-microsoft-azure Examples and Code Snippets
velero install \
--provider azure \
--plugins velero/velero-plugin-for-microsoft-azure:v1.4.0 \
--bucket $BLOB_CONTAINER \
--secret-file ./credentials-velero \
--backup-location-config resourceGroup=$AZURE_BACKUP_RESOURCE_GROUP,st
AZURE_BACKUP_RESOURCE_GROUP=Velero_Backups
az group create -n $AZURE_BACKUP_RESOURCE_GROUP --location WestUS
AZURE_STORAGE_ACCOUNT_ID="velero$(uuidgen | cut -d '-' -f5 | tr '[A-Z]' '[a-z]')"
az storage account create \
--name $AZURE_STORAGE_ACCO
velero backup-location create \
--provider azure \
--bucket $BLOB_CONTAINER \
--config resourceGroup=$AZURE_BACKUP_RESOURCE_GROUP,storageAccount=$AZURE_STORAGE_ACCOUNT_ID[,subscriptionId=$AZURE_BACKUP_SUBSCRIPTION_ID] \
--credential=bsl-cred
Community Discussions
Trending Discussions on velero-plugin-for-microsoft-azure
QUESTION
After the upgrade of velero from 1.3.2 to 1.7.7 backups started failing. When describing the failing backup:
...ANSWER
Answered 2022-Feb-13 at 13:37Not sure if this solves the issue for everyone, but it worked for me. After searching inside the velero source code repo, I located the following go package velero/pkg/cmd/util/output/backup_describer.go that contained the error message I found when describing the failing backup.
The hints at (2) in the source code led me to search on upload issues. As I am using the velero-plugin-for-microsoft-azure to handle uploads to Azure the following GitHub issue finally gave me the nudge in the right direction.
Seems like the velero-plugin-for-microsoft-azure required more memory (512Mi) since v1.5.3 (if I understood it correctly).
The limits on my one were still at 256Mi and failing, I increased the limits to 512Mi and, presto! It started working again.
A big shout out to David L. Smith-Uchida whose breadcrumbs led me to the solution!
QUESTION
i'm trying to use Velero to backup an AKS cluster but for some reason i'm unable to set the backup location in velero.
I can confirm the credentials-velero file I have obtains the correct storage access key, and the secret (cloud-credentials) reflects it as well.
Kind of at a lost as to why it's throwing me this error. Never used Velero before.
EDIT:
So I used the following commands to get the credential file:
Obtain the Azure Storage account access key
...ANSWER
Answered 2022-Jan-08 at 06:43not sure how your cred file formatting is and the command you are running.
Please try the below file and update the command as per need.
Example command :
QUESTION
I have an Azure Kubernetes cluster with Velero installed. A Service Principal was created for Velero, per option 1 of the instructions.
Velero was working fine until the credentials for the Service Principal were reset. Now the scheduled backups are failing.
...ANSWER
Answered 2021-Aug-01 at 22:29Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install velero-plugin-for-microsoft-azure
Create an Azure storage account and blob container
Get the resource group containing your VMs and disks
Set permissions for Velero
Install and start Velero
Install Velero, including all prerequisites, into the cluster and start the deployment. This will create a namespace called velero, and place a deployment named velero in it. If you're using AAD Pod Identity, you now need to add the aadpodidbinding=$IDENTITY_NAME label to the Velero pod(s), preferably through the Deployment's pod template. Additionally, you can specify --use-restic to enable restic support, and --wait to wait for the deployment to be ready.
For more complex installation needs, use either the Helm chart, or add --dry-run -o yaml options for generating the YAML representation for the installation.
Specify additional configurable parameters for the --backup-location-config flag.
Specify additional configurable parameters for the --snapshot-location-config flag.
Customize the Velero installation further to meet your needs.
Velero does not officially support for Windows containers. If your cluster has both Windows and Linux agent pool, add a node selector to the velero deployment to run Velero only on the Linux nodes. This can be done using the below command. kubectl patch deploy velero --namespace velero --type merge --patch '{ \"spec\": { \"template\": { \"spec\": { \"nodeSelector\": { \"beta.kubernetes.io/os\": \"linux\"} } } } }'
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page