Skip to content

Commit facf0b2

Browse files
committed
managed identity role note
1 parent 31b63ed commit facf0b2

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/azure-arc/kubernetes/conceptual-gitops-flux2.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "GitOps Flux v2 configurations with AKS and Azure Arc-enabled Kubernetes"
33
description: "This article provides a conceptual overview of GitOps in Azure for use in Azure Arc-enabled Kubernetes and Azure Kubernetes Service (AKS) clusters."
4-
ms.date: 02/07/2023
4+
ms.date: 03/14/2023
55
ms.topic: conceptual
66
ms.custom: devx-track-azurecli
77
---
@@ -364,6 +364,9 @@ If you use a `azblob` source, here are the blob-specific command arguments.
364364
| `--sas_token` | String | The Azure Blob SAS Token for authentication |
365365
| `--mi_client_id` | String | The client ID of the managed identity for authentication with Azure Blob |
366366

367+
> [!IMPORTANT]
368+
> When using managed identity authentication for AKS clusters, the `Storage Blob Contributor` role is assigned to the managed identity. Authentication using a managed identity is not yet available for Azure Arc0enabled Kubernetes clusters.
369+
367370
### Local secret for authentication with source
368371

369372
You can use a local Kubernetes secret for authentication with a `git`, `bucket` or `azBlob` source. The local secret must contain all of the authentication parameters needed for the source and must be created in the same namespace as the Flux configuration.

0 commit comments

Comments
 (0)