From 6e9303efe097d111f0c5e523aeb2fa75dbf7073f Mon Sep 17 00:00:00 2001 From: Tom Kerkhove Date: Tue, 13 Sep 2022 07:15:47 +0200 Subject: [PATCH] fix: Identity segregation is not supported in KEDA v2.7 Relates to https://github.com/kedacore/keda/issues/2656 Signed-off-by: Tom Kerkhove --- .../docs/2.7/authentication-providers/azure-ad-pod-identity.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/docs/2.7/authentication-providers/azure-ad-pod-identity.md b/content/docs/2.7/authentication-providers/azure-ad-pod-identity.md index 4c46c57f5..baf9d7306 100644 --- a/content/docs/2.7/authentication-providers/azure-ad-pod-identity.md +++ b/content/docs/2.7/authentication-providers/azure-ad-pod-identity.md @@ -9,9 +9,6 @@ You can tell KEDA to use Azure AD Pod Identity via `podIdentity.provider`. ```yaml podIdentity: provider: azure # Optional. Default: none - identityId: # Optional. Default: Identity linked with the label set when installing KEDA. ``` Azure AD Pod Identity will give access to containers with a defined label for `aadpodidbinding`. You can set this label on the KEDA operator deployment. This can be done for you during deployment with Helm with `--set podIdentity.activeDirectory.identity={your-label-name}`. - -You can override the identity that was assigned to KEDA during installation, by specifying an `identityId` parameter under the `podIdentity` field. This allows end-users to use different identities to access various resources which is more secure than using a single identity that has access to multiple resources.