You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both Kopia repository and Azure plugin need to interact with Azure storage. In order to keep in sync with the new features for both these two places and remove duplicated code, PR vmware-tanzu/velero#6686 makes the common code as util functions in Velero repository.
This commit refactors the Azure plugin based on these util functions.
Signed-off-by: Wenkai Yin(尹文开) <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+4-7
Original file line number
Diff line number
Diff line change
@@ -287,11 +287,10 @@ There are two ways to specify the role: use the built-in role or create a custom
287
287
AZURE_CLIENT_SECRET=${AZURE_CLIENT_SECRET}
288
288
AZURE_RESOURCE_GROUP=${AZURE_RESOURCE_GROUP}
289
289
AZURE_CLOUD_NAME=AzurePublicCloud
290
-
AZURE_ENVIRONMENT=AzurePublicCloud
291
290
EOF
292
291
```
293
292
294
-
> Available values for `AZURE_CLOUD_NAME` and `AZURE_ENVIRONMENT`: `AzurePublicCloud`, `AzureUSGovernmentCloud`, `AzureChinaCloud`. `AZURE_ENVIRONMENT` is NOT required for `AzurePublicCloud`
293
+
> Available values for `AZURE_CLOUD_NAME`: `AzurePublicCloud`, `AzureUSGovernmentCloud`, `AzureChinaCloud`
295
294
296
295
### Option 2: Use Azure AD Workload Identity
297
296
@@ -395,11 +394,10 @@ Before proceeding, ensure that you have installed [workload identity mutating ad
395
394
AZURE_SUBSCRIPTION_ID=${AZURE_SUBSCRIPTION_ID}
396
395
AZURE_RESOURCE_GROUP=${AZURE_RESOURCE_GROUP}
397
396
AZURE_CLOUD_NAME=AzurePublicCloud
398
-
AZURE_ENVIRONMENT=AzurePublicCloud
399
397
EOF
400
398
```
401
399
402
-
> Available values for `AZURE_CLOUD_NAME` and `AZURE_ENVIRONMENT`: `AzurePublicCloud`, `AzureUSGovernmentCloud`, `AzureChinaCloud`. `AZURE_ENVIRONMENT` is NOT required for `AzurePublicCloud`
400
+
> Available values for `AZURE_CLOUD_NAME`: `AzurePublicCloud`, `AzureUSGovernmentCloud`, `AzureChinaCloud`
403
401
404
402
405
403
### Option 3: Use storage account access key
@@ -418,11 +416,10 @@ _Note: this option is **not valid** if you are planning to take Azure snapshots
> Available values for `AZURE_CLOUD_NAME` and `AZURE_ENVIRONMENT`: `AzurePublicCloud`, `AzureUSGovernmentCloud`, `AzureChinaCloud`. `AZURE_ENVIRONMENT` is NOT required for `AzurePublicCloud`
422
+
> Available values for `AZURE_CLOUD_NAME`: `AzurePublicCloud`, `AzureUSGovernmentCloud`, `AzureChinaCloud`
426
423
427
424
## Install and start Velero
428
425
@@ -491,7 +488,7 @@ After that update your velero BackupStorageLocation with the useAAD flag as show
491
488
velero backup-location set default --provider azure --bucket $BLOB_CONTAINER --config useAAD="true",resourceGroup=$AZURE_BACKUP_RESOURCE_GROUP,storageAccount=$AZURE_STORAGE_ACCOUNT_ID[,subscriptionId=$AZURE_BACKUP_SUBSCRIPTION_ID]
492
489
```
493
490
494
-
Limitation: Listing storage account access key is still needed for Restic/Kopia to work as expected on Azure. Tracking Issue: [#5984](https://github.com/vmware-tanzu/velero/issues/5984). The useAAD route won't accrue to them and users using kopia/restic should not remove the ListKeys permission from the velero identity.
491
+
Limitation: Listing storage account access key is still needed for Restic to work as expected on Azure. The useAAD route won't accrue to it and users using Restic should not remove the ListKeys permission from the velero identity.
495
492
496
493
### If using storage account access key and no Azure snapshots:
0 commit comments