From 8de6690d7a49040f67f3b12db89737b1a7223394 Mon Sep 17 00:00:00 2001 From: Markus Blaschke Date: Wed, 17 May 2023 21:42:26 +0200 Subject: [PATCH] Update docs/book/src/troubleshooting.md Co-authored-by: Anish Ramasekar --- docs/book/src/troubleshooting.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/book/src/troubleshooting.md b/docs/book/src/troubleshooting.md index 3dea79c9e..d5f38007f 100644 --- a/docs/book/src/troubleshooting.md +++ b/docs/book/src/troubleshooting.md @@ -71,7 +71,6 @@ curl ${SERVICE_ACCOUNT_ISSUER}/.well-known/openid-configuration curl ${SERVICE_ACCOUNT_ISSUER}/openid/v1/jwks ``` -In a managed AKS cluster you also can get this OIDC issuer endpoint from the cluster json representation in ``properties.oidcIssuerProfile.issuerURL`` (you have to set API version to at least 2022-09-01). To test the endpoint try to access ``${AKS_oidcIssuerProfile_issuerURL}/.well-known/openid-configuration`` and you should get the OIDC configuration. If you can an error your OIDC endpoint deployment was failing. If you're seeing this issue with an AKS cluster, to resolve the issue try to reconcile the cluster by running [`az aks update`](https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-update). If the issue persists after reconciliation, create an [Azure support ticket](https://azure.microsoft.com/en-us/support/create-ticket). ## Workload pod doesn't have the Azure specific environment variables and projected service account token volume after upgrading to v1.0.0