Skip to content

Commit e8cf5ec

Browse files
Merge pull request #270467 from AbhishekMallick-MS/Mar-28-2024-AKS
AKS backup - concept updates
2 parents ff8db80 + 993a7cd commit e8cf5ec

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/backup/azure-kubernetes-service-cluster-backup-concept.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.topic: conceptual
55
ms.service: backup
66
ms.custom:
77
- ignite-2023
8-
ms.date: 02/27/2024
8+
ms.date: 03/28/2024
99
author: AbhishekMallick-MS
1010
ms.author: v-abhmallick
1111
---
@@ -25,7 +25,7 @@ Azure Backup now allows you to back up AKS clusters (cluster resources and persi
2525

2626
- Backup Extension is installed in its own namespace *dataprotection-microsoft* by default. It's installed with cluster wide scope that allows the extension to access all the cluster resources. During the extension installation, it also creates a User-assigned Managed Identity (Extension Identity) in the Node Pool resource group.
2727

28-
- Backup Extension uses a blob container (provided in input during installation) as a default location for backup storage. To access this blob container, the Extension Identity requires *Storage Account Contributor* role on the storage account that has the container.
28+
- Backup Extension uses a blob container (provided in input during installation) as a default location for backup storage. To access this blob container, the Extension Identity requires *Storage Blob Data Contributor* role on the storage account that has the container.
2929

3030
- You need to install Backup Extension on both the source cluster to be backed up and the target cluster where the restore will happen.
3131

@@ -38,6 +38,8 @@ Azure Backup now allows you to back up AKS clusters (cluster resources and persi
3838
>[!Note]
3939
>Both of these core components are deployed with aggressive hard limits on CPU and memory, with CPU *less than 0.5% of a core* and memory limit ranging from *50-200 MB*. So, the *COGS impact* of these components is very low. Because they are core platform components, there is no workaround available to remove them once installed in the cluster.
4040
41+
- If Storage Account, to be provided as input for Extension installation, is under Virtual Network/Firewall, then BackupVault needs to be added as trusted access in Storage Account Network Settings. [Learn how to grant access to trusted Azure service](../storage/common/storage-network-security.md?tabs=azure-portal#grant-access-to-trusted-azure-services), which helps to store backups in the Vault datastore
42+
4143
Learn [how to manage the operation to install Backup Extension using Azure CLI](azure-kubernetes-service-cluster-manage-backups.md#backup-extension-related-operations).
4244

4345
## Trusted Access

0 commit comments

Comments
 (0)