Skip to content

Commit 759f965

Browse files
Merge pull request #226715 from MGoedtel/bug63122
fixed broken link and syntax with Kubectl command
2 parents a8aa387 + 6268faa commit 759f965

File tree

3 files changed

+5
-7
lines changed

3 files changed

+5
-7
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: Deploy and configure an Azure Kubernetes Service (AKS) cluster with workload identity (preview)
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).
4-
services: container-service
54
ms.topic: article
65
ms.date: 01/11/2023
76
---

articles/aks/workload-identity-migrate-from-pod-identity.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
2-
title: Modernize your Azure Kubernetes Service (AKS) application to use workload identity
2+
title: Modernize your Azure Kubernetes Service (AKS) application to use workload identity (preview)
33
description: In this Azure Kubernetes Service (AKS) article, you learn how to configure your Azure Kubernetes Service pod to authenticate with workload identity.
4-
services: container-service
54
ms.topic: article
6-
ms.date: 11/3/2022
5+
ms.date: 02/08/2023
76
---
87

9-
# Modernize application authentication with workload identity
8+
# Modernize application authentication with workload identity (preview)
109

1110
This article focuses on pod-managed identity migration to Azure Active Directory (Azure AD) workload identity (preview) for your Azure Kubernetes Service (AKS) cluster. It also provides guidance depending on the version of the [Azure Identity][azure-identity-supported-versions] client library used by your container-based application.
1211

@@ -164,7 +163,7 @@ spec:
164163
This configuration applies to any configuration where a pod is being created. After updating or deploying your application, you can verify the pod is in a running state using the [kubectl describe pod][kubectl-describe] command. Replace the value `podName` with the image name of your deployed pod.
165164

166165
```bash
167-
kubectl describe pods podName -c azwi-proxy
166+
kubectl describe pods podName
168167
```
169168

170169
To verify that pod is passing IMDS transactions, use the [kubectl logs][kubelet-logs] command. Replace the value `podName` with the image name of your deployed pod:
@@ -211,3 +210,4 @@ This article showed you how to set up your pod to authenticate using a workload
211210

212211
<!-- EXTERNAL LINKS -->
213212
[kubectl-describe]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#describe
213+
[kubelet-logs]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#logs

articles/aks/workload-identity-overview.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: Use an Azure AD workload identities (preview) on Azure Kubernetes Service (AKS)
33
description: Learn about Azure Active Directory workload identity (preview) for Azure Kubernetes Service (AKS) and how to migrate your application to authenticate using this identity.
4-
services: container-service
54
ms.topic: article
65
ms.date: 01/06/2023
76
author: mgoedtel

0 commit comments

Comments
 (0)