Merge pull request #276666 from tamram/tamram24-0529

fix pod name typo

Author: prmerger-automator[bot]

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

@@ -44,7 +44,7 @@ az account set --subscription <subscription-id>
 
 To help simplify steps to configure the identities required, the steps below define environment variables that are referenced in the examples in this article. Remember to replace the values shown with your own values:
 
-  ```bash
+  ```azurecli-interactive
   export RESOURCE_GROUP="myResourceGroup"
   export LOCATION="eastus"
   export CLUSTER_NAME="myAKSCluster"
@@ -117,7 +117,7 @@ az aks update \
 
 To get the OIDC issuer URL and save it to an environmental variable, run the following command:
 
-```bash
+```azurecli-interactive
 export AKS_OIDC_ISSUER="$(az aks show --name "${CLUSTER_NAME}" \
     --resource-group "${RESOURCE_GROUP}" \
     --query "oidcIssuerProfile.issuerUrl" \
@@ -146,7 +146,7 @@ az identity create \
 
 Next, create a variable for the managed identity's client ID.
 
-```bash
+```azurecli-interactive
 export USER_ASSIGNED_CLIENT_ID="$(az identity show \
     --resource-group "${RESOURCE_GROUP}" \
     --name "${USER_ASSIGNED_IDENTITY_NAME}" \
@@ -164,7 +164,7 @@ az aks get-credentials --name "${CLUSTER_NAME}" --resource-group "${RESOURCE_GRO
 
 Copy and paste the following multi-line input in the Azure CLI.
 
-```bash
+```azurecli-interactive
 cat <<EOF | kubectl apply -f -
 apiVersion: v1
 kind: ServiceAccount
@@ -321,8 +321,8 @@ The following example shows how to use the Azure role-based access control (Azur
 
 To check whether all properties are injected properly by the webhook, use the [kubectl describe][kubectl-describe] command:
 
-```bash
-kubectl describe pod quick-start | grep "SECRET_NAME:"
+```azurecli-interactive
+kubectl describe pod sample-workload-identity-key-vault | grep "SECRET_NAME:"
 ```
 
 If successful, the output should be similar to the following:
@@ -333,8 +333,8 @@ If successful, the output should be similar to the following:
 
 To verify that pod is able to get a token and access the resource, use the kubectl logs command:
 
-```bash
-kubectl logs quick-start
+```azurecli-interactive
+kubectl logs sample-workload-identity-key-vault
 ```
 
 If successful, the output should be similar to the following: