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
Copy file name to clipboardExpand all lines: articles/backup/azure-kubernetes-service-cluster-backup-concept.md
+20-19Lines changed: 20 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Azure Kubernetes Service (AKS) backup using Azure Backup overview
3
3
description: This article explains the concept of Azure Kubernetes Service (AKS) backup using Azure Backup.
4
4
ms.topic: conceptual
5
5
ms.service: backup
6
-
ms.date: 02/28/2023
6
+
ms.date: 03/03/2023
7
7
author: jyothisuri
8
8
ms.author: jsuri
9
9
---
@@ -24,15 +24,15 @@ This section explains the least privileged security models required for a Backup
24
24
25
25
- 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.
26
26
27
-
-Backup Extension also needs to be installed on both the source cluster to be backed up and the target cluster where the restore will happen.
27
+
-You need to install Backup Extension on both the source cluster to be backed up and the target cluster where the restore will happen.
28
28
29
-
Learn [how to manage the operation to install Backup Extension using Azure CLI](azure-kubernetes-service-cluster-manage-backups.md#manage-azure-kubernetes-service-cluster-backups-using-azure-backup-preview).
29
+
Learn [how to manage the operation to install Backup Extension using Azure CLI](azure-kubernetes-service-cluster-manage-backups.md#manage-operations).
30
30
31
31
### Trusted Access
32
32
33
-
Many Azure services depend on *clusterAdmin kubeconfig* and the *publicly accessible kube-apiserver endpoint* to access AKS clusters. The **AKS Trusted Access** feature enables you to bypass the private endpoint restriction. Without using Microsoft Azure Active Directory (Azure AD) application, this feature enables you to give explicit consent to your system-assigned identity of allowed resources to access your AKS clusters using an Azure resource RoleBinding.
33
+
Many Azure services depend on *clusterAdmin kubeconfig* and the *publicly accessible kube-apiserver endpoint* to access AKS clusters. The **AKS Trusted Access** feature enables you to bypass the private endpoint restriction. Without using Microsoft Azure Active Directory (Azure AD) application, this feature enables you to give explicit consent to your system-assigned identity of allowed resources to access your AKS clusters using an Azure resource RoleBinding. The Trusted Access feature allows you to access AKS clusters with different configurations, which isn’t limited to private clusters, clusters with local accounts disabled, Azure AD clusters, and authorized IP range clusters.
34
34
35
-
Your Azure resources access AKS clusters through the AKS regional gateway via system-assigned Managed Identity authentication with the appropriate Kubernetes permissions via an Azure resource role. The Trusted Access feature allows you to access AKS clusters with different configurations, which aren't limited to private clusters, clusters with local accounts disabled, Azure AD clusters, and authorized IP range clusters.
35
+
Your Azure resources access AKS clusters through the AKS regional gateway using system-assigned managed identity authentication. The managed identity must have the appropriate Kubernetes permissions assigned via an Azure resource role.
36
36
37
37
For AKS backup, the Backup vault accesses your AKS clusters via Trusted Access to configure backups and restores. The Backup vault is assigned a pre-defined role **Microsoft.DataProtection/backupVaults/backup-operator** in the AKS cluster, allowing it to only perform specific backup operations.
38
38
@@ -42,10 +42,11 @@ Learn [how to enable Trusted Access](azure-kubernetes-service-cluster-manage-bac
42
42
43
43
To enable backup for an AKS cluster, see the following prerequisites: .
44
44
45
-
- AKS backup uses CSI drivers snapshot capabilities to perform backups of Persistent Volumes. CSI Driver support is available for AKS clusters with Kubernetes version *1.21.1* or later.
46
-
- Currently, AKS backup only supports backup of Azure Disk based Persistent Volumes (enabled by CSI Driver). If you’re using Azure File Share and Azure Blob type Persistent Volumes in your AKS clusters, you can configure backups for them via the Azure Backup solutions available for [Azure File Share](azure-file-share-backup-overview.md) and [Azure Blob](blob-backup-overview.md).
45
+
- AKS backup uses CSI drivers snapshot capabilities to perform backups of persistent volumes. CSI Driver support is available for AKS clusters with Kubernetes version *1.21.1* or later.
47
46
48
-
- In Tree, volumes aren't supported by AKS backup; only CSI driver based volumes can be backed up. You can [migrate from tree volumes to CSI driver based Persistent Volumes](../aks/csi-migrate-in-tree-volumes.md).
47
+
>[!Note]
48
+
>- Currently, AKS backup only supports backup of Azure Disk based persistent volumes (enabled by CSI driver). If you're using Azure File Share and Azure Blob type persistent volumes in your AKS clusters, you can configure backups for them via the Azure Backup solutions available for [Azure File Share](azure-file-share-backup-overview.md) and [Azure Blob](blob-backup-overview.md).
49
+
>- In Tree, volumes aren't supported by AKS backup; only CSI driver based volumes can be backed up. You can [migrate from tree volumes to CSI driver based Persistent Volumes](../aks/csi-migrate-in-tree-volumes.md).
49
50
50
51
- Before installing Backup Extension in the AKS cluster, ensure that the CSI drivers and snapshots are enabled for your cluster. If disabled, see [these steps to enable them](../aks/csi-storage-drivers.md#enable-csi-storage-drivers-on-an-existing-cluster).
51
52
@@ -60,24 +61,24 @@ To enable backup for an AKS cluster, see the following prerequisites: .
60
61
61
62
To perform AKS backup and restore operations as a user, you need to have specific roles on the AKS cluster, Backup vault, Storage account, and Snapshot resource group.
62
63
63
-
| Scope | Preferred Role |Reason|
64
+
| Scope | Preferred Role |Description|
64
65
| --- | --- | --- |
65
-
| AKS Cluster |Owner | Owner role allows you to install Backup Extension, enable *Trusted Access* and grant permissions to Backup vault over cluster. |
66
-
| Backup vault resource group | Backup Contributor |This role allows you to create Backup vault in a resource group, create backup policy, configure backup, and restore and assign missing roles required for Backup operations. |
67
-
| Storage account | Owner |Owner role allows you to perform read and write operations on the storage account and assign required roles to other Azure resources as a part of backup operations. |
68
-
| Snapshot resource group | Owner |Owner role allows you to perform read and write operations on the Snapshot resource group and assign required roles to other Azure resources as part of backup operations. |
66
+
| AKS Cluster |Allows you to install Backup Extension, enable *Trusted Access* and grant permissions to Backup vault over the cluster. |
67
+
| Backup vault resource group | Backup Contributor |Allows you to create Backup vault in a resource group, create backup policy, configure backup, and restore and assign missing roles required for Backup operations. |
68
+
| Storage account | Owner |Allows you to perform read and write operations on the storage account and assign required roles to other Azure resources as a part of backup operations. |
69
+
| Snapshot resource group | Owner |Allows you to perform read and write operations on the Snapshot resource group and assign required roles to other Azure resources as part of backup operations. |
69
70
70
71
>[!Note]
71
-
>Owner role on an Azure resource allows you to perform Azure RBAC operations of that resource. If it's not available, you need to get the *resource owner*to provide the required roles to the Backup vault and AKS cluster before initiating the backup or restore operations.
72
+
>Owner role on an Azure resource allows you to perform Azure RBAC operations of that resource. If it's not available, the *resource owner*must provide the required roles to the Backup vault and AKS cluster before initiating the backup or restore operations.
72
73
73
74
Also, as part of the backup and restore operations, the following roles are assigned to the AKS cluster, Backup Extension Identity, and Backup vault.
74
75
75
-
| Role | Assigned To | Assigned on |Reason|
76
+
| Role | Assigned To | Assigned on |Description|
76
77
| --- | --- | --- | --- |
77
-
| Reader | Backup vault | AKS cluster |This role allows the Backup vault to perform list and read operations on AKS cluster. |
78
-
| Reader | Backup vault | Snapshot resource group |This role allows the Backup vault to perform list and read operations on snapshot resource group. |
79
-
| Disk Snapshot Contributor | AKS cluster | Snapshot resource group |This role allows AKS cluster to store persistent volume snapshots in the resource group. |
80
-
| Storage Account Contributor | Extension Identity | Storage account |This role allows Backup Extension to store cluster resource backups in the blob container. |
78
+
| Reader | Backup vault | AKS cluster |Allows the Backup vault to perform list and read operations on AKS cluster. |
79
+
| Reader | Backup vault | Snapshot resource group |Allows the Backup vault to perform list and read operations on snapshot resource group. |
80
+
| Disk Snapshot Contributor | AKS cluster | Snapshot resource group |Allows AKS cluster to store persistent volume snapshots in the resource group. |
81
+
| Storage Account Contributor | Extension Identity | Storage account |Allows Backup Extension to store cluster resource backups in the blob container. |
81
82
82
83
>[!Note]
83
84
>AKS backup allows you to assign these roles during backup and restore processes through the Azure portal with a single click.
Copy file name to clipboardExpand all lines: articles/backup/azure-kubernetes-service-cluster-backup.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Back up Azure Kubernetes Service (AKS) using Azure Backup
3
3
description: This article explains how to back up Azure Kubernetes Service (AKS) using Azure Backup.
4
4
ms.topic: how-to
5
5
ms.service: backup
6
-
ms.date: 02/28/2023
6
+
ms.date: 03/03/2023
7
7
author: jyothisuri
8
8
ms.author: jsuri
9
9
---
@@ -92,7 +92,7 @@ To configure backups for AKS cluster, follow these steps:
92
92
6. In the *context* pane, provide the *storage account* and *blob container* where you need to store the backup, and then select **Generate Command**.
93
93
94
94
>[!Note]
95
-
>Before you install the AKS Backup Extension via *Azure CLI*, you must enable the `Microsoft.KubernetesConfiguration` resource provider on the subscription. We don't recommend to proceed with the Backup Extension installation before enabling the resource provider.
95
+
>Before you install the AKS Backup Extension via *Azure CLI*, you must enable the `Microsoft.KubernetesConfiguration` resource provider on the subscription.
96
96
>
97
97
>To register the resource provider before the extension installation (don't initiate extension installation before registering resource provider), run the following commands:
98
98
>
@@ -101,21 +101,22 @@ To configure backups for AKS cluster, follow these steps:
101
101
>2. Monitor the registration process. The registration may take up to *10 minutes*.
102
102
> `az provider show -n Microsoft.KubernetesConfiguration -o table`
103
103
104
-
7. Open the PowerShell console, sign in to the Azure portal (`az login`), and then copy and run the generated commands.
104
+
7. Open the PowerShell console, and then upgrade the CLI to version *2.24.0* or later using the command `az upgrade`.
105
+
106
+
Sign in to the Azure portal (using the command `az login`), and then copy and run the generated commands.
105
107
106
108
The commands install the *Backup Extension* and *Assign Extension* managed identity permissions on the storage account.
107
109
108
110
Once done, select **Revalidate**.
109
111
110
112
>[!Note]
111
-
>1. Before you run the Azure CLI command, upgrade the CLI to version *2.24.0* or later using the command `az upgrade`.
112
-
>2. We're using the Extension managed identity attached to the underlying compute of the AKS cluster. After running the `az role assignment` command, it may take some time (up to *1 hour*) to propagate permission to the AKS cluster (due to caching issue). If revalidation fails, try again after some time.
113
+
>We're using the Extension managed identity attached to the underlying compute of the AKS cluster. After running the `az role assignment` command, it may take some time (up to *1 hour*) to propagate permission to the AKS cluster (due to caching issue). If revalidation fails, try again after some time.
113
114
114
115
8. To enable *Trusted Access* and *other role permissions*, select **Grant Permission** > **Next**.
115
116
116
117
9. Select the backup policy that defines the schedule and retention policy for AKS backup, and then select **Next**.
117
118
118
-
10. Select **Add/Edit** to define the **Backup Instance Configuration**.
119
+
10. Select **Add/Edit** to define the *backup instance configuration*.
119
120
120
121
11. In the *context* pane, enter the *cluster resources* that you want to back up.
0 commit comments