|
2 | 2 | title: Use Azure Key Vault Secrets Provider extension to fetch secrets into Azure Arc-enabled Kubernetes clusters
|
3 | 3 | description: Learn how to set up the Azure Key Vault Provider for Secrets Store CSI Driver interface as an extension on Azure Arc enabled Kubernetes cluster
|
4 | 4 | ms.custom: devx-track-azurecli
|
5 |
| -ms.date: 02/09/2024 |
| 5 | +ms.date: 06/03/2024 |
6 | 6 | ms.topic: how-to
|
7 | 7 | ---
|
8 | 8 |
|
@@ -47,11 +47,11 @@ Only one instance of the extension can be deployed on each Azure Arc-enabled Kub
|
47 | 47 | 1. In the [Azure portal](https://portal.azure.com/#home), navigate to **Kubernetes - Azure Arc** and select your cluster.
|
48 | 48 | 1. Select **Extensions** (under **Settings**), and then select **+ Add**.
|
49 | 49 |
|
50 |
| - [](media/tutorial-akv-secrets-provider/extension-install-add-button.jpg#lightbox) |
| 50 | + :::image type="content" source="media/tutorial-akv-secrets-provider/extension-install-add-button.png" lightbox="media/tutorial-akv-secrets-provider/extension-install-add-button.png" alt-text="Screenshot showing the Extensions pane for an Arc-enabled Kubernetes cluster in the Azure portal."::: |
51 | 51 |
|
52 | 52 | 1. From the list of available extensions, select **Azure Key Vault Secrets Provider** to deploy the latest version of the extension.
|
53 | 53 |
|
54 |
| - [](media/tutorial-akv-secrets-provider/extension-install-new-resource.jpg) |
| 54 | + :::image type="content" source="media/tutorial-akv-secrets-provider/extension-install-new-resource.png" alt-text="Screenshot showing the Azure Key Vault Secrets Provider extension in the Azure portal."::: |
55 | 55 |
|
56 | 56 | 1. Follow the prompts to deploy the extension. If needed, customize the installation by changing the default options on the **Configuration** tab.
|
57 | 57 |
|
@@ -279,7 +279,7 @@ Before you move on to the next section, take note of the following properties:
|
279 | 279 |
|
280 | 280 | Currently, the Secrets Store CSI Driver on Arc-enabled clusters can be accessed through a service principal. Follow these steps to provide an identity that can access your Key Vault.
|
281 | 281 |
|
282 |
| -1. Follow the steps [to create a service principal in Azure](../../active-directory/develop/howto-create-service-principal-portal.md#register-an-application-with-azure-ad-and-create-a-service-principal). Take note of the Client ID and Client Secret generated in this step. |
| 282 | +1. Follow the steps [to create a service principal in Azure](/entra/identity-platform/howto-create-service-principal-portal). Take note of the Client ID and Client Secret generated in this step. |
283 | 283 | 1. Next, [ensure Azure Key Vault has GET permission to the created service principal](../../key-vault/general/assign-access-policy.md#assign-an-access-policy).
|
284 | 284 | 1. Use the client ID and Client Secret from the first step to create a Kubernetes secret on the connected cluster:
|
285 | 285 |
|
|
0 commit comments