Skip to content

Commit 59ee3d1

Browse files
authored
Update workload-identity-deploy-cluster.md
1 parent 2df6dcd commit 59ee3d1

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

articles/aks/workload-identity-deploy-cluster.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Deploy and configure an Azure Kubernetes Service (AKS) cluster with workl
33
description: In this Azure Kubernetes Service (AKS) article, you deploy an Azure Kubernetes Service cluster and configure it with an Azure AD workload identity (preview).
44
services: container-service
55
ms.topic: article
6-
ms.date: 01/06/2023
6+
ms.date: 01/11/2023
77
---
88

99
# Deploy and configure workload identity (preview) on an Azure Kubernetes Service (AKS) cluster
@@ -157,6 +157,15 @@ az identity federated-credential create --name myfederatedIdentity --identity-na
157157
> [!NOTE]
158158
> It takes a few seconds for the federated identity credential to be propagated after being initially added. If a token request is made immediately after adding the federated identity credential, it might lead to failure for a couple of minutes as the cache is populated in the directory with old data. To avoid this issue, you can add a slight delay after adding the federated identity credential.
159159
160+
## Deploy your application
161+
162+
> [!IMPORTANT]
163+
> Ensure your application pods using workload identity have added the following label [azure.workload.identity/use: "true"] to your running pods/deployments, otherwise the pods will fail once restarted.
164+
165+
```azurecli-interactive
166+
kubectl apply -f <your application>
167+
```
168+
160169
## Disable workload identity
161170

162171
To disable the Azure AD workload identity on the AKS cluster where it's been enabled and configured, you can run the following command:

0 commit comments

Comments
 (0)