From 1a7270b9be27680e03efb851374117f0a6025417 Mon Sep 17 00:00:00 2001 From: Zbynek Roubalik Date: Thu, 3 Oct 2024 11:02:42 +0200 Subject: [PATCH] `azure` pod identity provider is not supported Signed-off-by: Zbynek Roubalik --- .../docs/2.15/authentication-providers/azure-key-vault.md | 2 +- content/docs/2.15/concepts/authentication.md | 6 +++--- content/docs/2.15/operate/cloud-events.md | 2 +- content/docs/2.15/scalers/azure-app-insights.md | 4 ++-- content/docs/2.15/scalers/azure-data-explorer.md | 4 ++-- content/docs/2.15/scalers/azure-event-hub.md | 4 ++-- content/docs/2.15/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.15/scalers/azure-monitor.md | 4 ++-- content/docs/2.15/scalers/azure-pipelines.md | 2 +- content/docs/2.15/scalers/azure-service-bus.md | 4 ++-- content/docs/2.15/scalers/azure-storage-blob.md | 4 ++-- content/docs/2.15/scalers/azure-storage-queue.md | 4 ++-- content/docs/2.15/scalers/prometheus.md | 4 ++-- .../docs/2.16/authentication-providers/azure-key-vault.md | 2 +- content/docs/2.16/concepts/authentication.md | 6 +++--- content/docs/2.16/operate/cloud-events.md | 2 +- content/docs/2.16/scalers/azure-app-insights.md | 4 ++-- content/docs/2.16/scalers/azure-data-explorer.md | 4 ++-- content/docs/2.16/scalers/azure-event-hub.md | 4 ++-- content/docs/2.16/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.16/scalers/azure-monitor.md | 4 ++-- content/docs/2.16/scalers/azure-pipelines.md | 2 +- content/docs/2.16/scalers/azure-service-bus.md | 4 ++-- content/docs/2.16/scalers/azure-storage-blob.md | 4 ++-- content/docs/2.16/scalers/azure-storage-queue.md | 4 ++-- content/docs/2.16/scalers/prometheus.md | 4 ++-- 26 files changed, 48 insertions(+), 48 deletions(-) diff --git a/content/docs/2.15/authentication-providers/azure-key-vault.md b/content/docs/2.15/authentication-providers/azure-key-vault.md index 41b6588fb..674229956 100644 --- a/content/docs/2.15/authentication-providers/azure-key-vault.md +++ b/content/docs/2.15/authentication-providers/azure-key-vault.md @@ -20,7 +20,7 @@ The `cloud` parameter can be used to specify cloud environments besides `Azure P azureKeyVault: # Optional. vaultUri: {key-vault-address} # Required. podIdentity: # Optional. - provider: azure | azure-workload # Required. + provider: azure-workload # Required. identityId: # Optional credentials: # Optional. clientId: {azure-ad-client-id} # Required. diff --git a/content/docs/2.15/concepts/authentication.md b/content/docs/2.15/concepts/authentication.md index 6b602a8c4..d751e01ec 100644 --- a/content/docs/2.15/concepts/authentication.md +++ b/content/docs/2.15/concepts/authentication.md @@ -115,12 +115,12 @@ spec: serviceAccount: {path-to-service-account-file} # Optional. secrets: # Required. - parameter: {scaledObject-parameter-name} # Required. - key: {hashicorp-vault-secret-key-name} # Required. - path: {hashicorp-vault-secret-path} # Required. + key: {hashicorp-vault-secret-key-name} # Required. + path: {hashicorp-vault-secret-path} # Required. azureKeyVault: # Optional. vaultUri: {key-vault-address} # Required. podIdentity: # Optional. Required when using pod identity. - provider: azure | azure-workload # Required. + provider: azure-workload # Required. identityId: # Optional credentials: # Optional. Required when not using pod identity. clientId: {azure-ad-client-id} # Required. diff --git a/content/docs/2.15/operate/cloud-events.md b/content/docs/2.15/operate/cloud-events.md index ad46c74f1..80c9034d3 100644 --- a/content/docs/2.15/operate/cloud-events.md +++ b/content/docs/2.15/operate/cloud-events.md @@ -84,7 +84,7 @@ Here is an overview of the supported authentication types: - `accessKey` - Access key string for the Azure Event Grid connection auth. #### Pod identity based authentication -[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ```yaml apiVersion: keda.sh/v1alpha1 diff --git a/content/docs/2.15/scalers/azure-app-insights.md b/content/docs/2.15/scalers/azure-app-insights.md index 234a00f32..cf53d5e45 100644 --- a/content/docs/2.15/scalers/azure-app-insights.md +++ b/content/docs/2.15/scalers/azure-app-insights.md @@ -76,7 +76,7 @@ The principal will need `Monitoring Reader` access to query metrics from the App **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used in place of credential based authentication. The following section contains an example of a `TriggerAuthentication` using pod identity. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used in place of credential based authentication. The following section contains an example of a `TriggerAuthentication` using pod identity. ### Example @@ -112,7 +112,7 @@ spec: key: tenantId # or Pod Identity, kind: Secret is not required in case of pod Identity podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.15/scalers/azure-data-explorer.md b/content/docs/2.15/scalers/azure-data-explorer.md index 6493bafd1..787c05188 100644 --- a/content/docs/2.15/scalers/azure-data-explorer.md +++ b/content/docs/2.15/scalers/azure-data-explorer.md @@ -77,7 +77,7 @@ The AD identity that will be used requires `DatabaseViewer` role to query metric **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Examples @@ -144,7 +144,7 @@ metadata: name: azure-data-explorer-trigger-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.15/scalers/azure-event-hub.md b/content/docs/2.15/scalers/azure-event-hub.md index 926438526..cb1601cf3 100644 --- a/content/docs/2.15/scalers/azure-event-hub.md +++ b/content/docs/2.15/scalers/azure-event-hub.md @@ -80,7 +80,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ```yaml apiVersion: keda.sh/v1alpha1 @@ -90,7 +90,7 @@ metadata: namespace: default spec: podIdentity: - provider: Azure | azure-workload + provider: azure-workload ``` When you do so, the Event Hub scaler will depend on the existence of two configurations you have to provide: `eventHubNamespace` and `eventHubName`. You can also configure `storageAccountName` if you wish to use Azure AD Pod / Workload Identity to authenticate to Azure Blob Storage instead of a connection string. diff --git a/content/docs/2.15/scalers/azure-log-analytics.md b/content/docs/2.15/scalers/azure-log-analytics.md index c7743db27..26a75a522 100644 --- a/content/docs/2.15/scalers/azure-log-analytics.md +++ b/content/docs/2.15/scalers/azure-log-analytics.md @@ -152,7 +152,7 @@ You can use `TriggerAuthentication` CRD to configure the authentication by provi You can use managed identity to request access token for Log Analytics API. The advantage of this approach is that there is no need to store secrets in Kubernetes. Read [more](https://docs.microsoft.com/en-us/azure/aks/use-managed-identity) about managed identities in Azure Kubernetes Service. -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -248,7 +248,7 @@ metadata: namespace: kedaloganalytics spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.15/scalers/azure-monitor.md b/content/docs/2.15/scalers/azure-monitor.md index 156aa1099..330c583de 100644 --- a/content/docs/2.15/scalers/azure-monitor.md +++ b/content/docs/2.15/scalers/azure-monitor.md @@ -73,7 +73,7 @@ The user will need access to read data from the Azure resource. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -100,7 +100,7 @@ spec: key: activeDirectoryClientPassword # or Pod Identity, kind: Secret is not required in case of pod Identity podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.15/scalers/azure-pipelines.md b/content/docs/2.15/scalers/azure-pipelines.md index 3f8fa4373..cbb532b34 100644 --- a/content/docs/2.15/scalers/azure-pipelines.md +++ b/content/docs/2.15/scalers/azure-pipelines.md @@ -64,7 +64,7 @@ As an alternative to using environment variables, you can authenticate with Azur **Pod Identity Authentication** -[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### How to determine your pool ID diff --git a/content/docs/2.15/scalers/azure-service-bus.md b/content/docs/2.15/scalers/azure-service-bus.md index e7b9c6bf3..80873efbb 100644 --- a/content/docs/2.15/scalers/azure-service-bus.md +++ b/content/docs/2.15/scalers/azure-service-bus.md @@ -69,7 +69,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -82,7 +82,7 @@ metadata: name: azure-servicebus-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.15/scalers/azure-storage-blob.md b/content/docs/2.15/scalers/azure-storage-blob.md index 05bdbb220..1f895ad3b 100644 --- a/content/docs/2.15/scalers/azure-storage-blob.md +++ b/content/docs/2.15/scalers/azure-storage-blob.md @@ -56,7 +56,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod Identity Authentication** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. - `accountName` - Name of the Azure Storage Account. @@ -69,7 +69,7 @@ metadata: name: azure-blob-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.15/scalers/azure-storage-queue.md b/content/docs/2.15/scalers/azure-storage-queue.md index a95618537..ef55c5983 100644 --- a/content/docs/2.15/scalers/azure-storage-queue.md +++ b/content/docs/2.15/scalers/azure-storage-queue.md @@ -46,7 +46,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -57,7 +57,7 @@ metadata: name: azure-queue-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.15/scalers/prometheus.md b/content/docs/2.15/scalers/prometheus.md index a0750edd6..e72cf3668 100644 --- a/content/docs/2.15/scalers/prometheus.md +++ b/content/docs/2.15/scalers/prometheus.md @@ -87,7 +87,7 @@ To gain a better understanding of creating a Prometheus trigger for Amazon Manag #### Azure Monitor Managed Service for Prometheus Azure has a [managed service for Prometheus](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/prometheus-metrics-overview) and Prometheus scaler can be used to run prometheus query against that. -- [Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used in `authenticationRef` - see later in example. +- [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used in `authenticationRef` - see later in example. - `Monitoring Data Reader` role needs to be assigned to workload identity (or pod identity) on the `Azure Monitor Workspace`. - No other auth (via `authModes`) can be provided with Azure Pod/Workload Identity Auth. - Prometheus query endpoint can be retreived from [Azure Monitor Workspace](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/azure-monitor-workspace-overview) that was configured to ingest prometheus metrics. @@ -406,7 +406,7 @@ metadata: name: azure-managed-prometheus-trigger-auth spec: podIdentity: - provider: azure | azure-workload # use "azure" for pod identity and "azure-workload" for workload identity + provider: azure-workload identityId: # Optional. Default: Identity linked with the label set when installing KEDA. --- apiVersion: keda.sh/v1alpha1 diff --git a/content/docs/2.16/authentication-providers/azure-key-vault.md b/content/docs/2.16/authentication-providers/azure-key-vault.md index 41b6588fb..674229956 100644 --- a/content/docs/2.16/authentication-providers/azure-key-vault.md +++ b/content/docs/2.16/authentication-providers/azure-key-vault.md @@ -20,7 +20,7 @@ The `cloud` parameter can be used to specify cloud environments besides `Azure P azureKeyVault: # Optional. vaultUri: {key-vault-address} # Required. podIdentity: # Optional. - provider: azure | azure-workload # Required. + provider: azure-workload # Required. identityId: # Optional credentials: # Optional. clientId: {azure-ad-client-id} # Required. diff --git a/content/docs/2.16/concepts/authentication.md b/content/docs/2.16/concepts/authentication.md index 6b602a8c4..d751e01ec 100644 --- a/content/docs/2.16/concepts/authentication.md +++ b/content/docs/2.16/concepts/authentication.md @@ -115,12 +115,12 @@ spec: serviceAccount: {path-to-service-account-file} # Optional. secrets: # Required. - parameter: {scaledObject-parameter-name} # Required. - key: {hashicorp-vault-secret-key-name} # Required. - path: {hashicorp-vault-secret-path} # Required. + key: {hashicorp-vault-secret-key-name} # Required. + path: {hashicorp-vault-secret-path} # Required. azureKeyVault: # Optional. vaultUri: {key-vault-address} # Required. podIdentity: # Optional. Required when using pod identity. - provider: azure | azure-workload # Required. + provider: azure-workload # Required. identityId: # Optional credentials: # Optional. Required when not using pod identity. clientId: {azure-ad-client-id} # Required. diff --git a/content/docs/2.16/operate/cloud-events.md b/content/docs/2.16/operate/cloud-events.md index 7c93ebd8e..4ae54d5b5 100644 --- a/content/docs/2.16/operate/cloud-events.md +++ b/content/docs/2.16/operate/cloud-events.md @@ -84,7 +84,7 @@ Here is an overview of the supported authentication types: - `accessKey` - Access key string for the Azure Event Grid connection auth. #### Pod identity based authentication -[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ```yaml apiVersion: keda.sh/v1alpha1 diff --git a/content/docs/2.16/scalers/azure-app-insights.md b/content/docs/2.16/scalers/azure-app-insights.md index 234a00f32..cf53d5e45 100644 --- a/content/docs/2.16/scalers/azure-app-insights.md +++ b/content/docs/2.16/scalers/azure-app-insights.md @@ -76,7 +76,7 @@ The principal will need `Monitoring Reader` access to query metrics from the App **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used in place of credential based authentication. The following section contains an example of a `TriggerAuthentication` using pod identity. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used in place of credential based authentication. The following section contains an example of a `TriggerAuthentication` using pod identity. ### Example @@ -112,7 +112,7 @@ spec: key: tenantId # or Pod Identity, kind: Secret is not required in case of pod Identity podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.16/scalers/azure-data-explorer.md b/content/docs/2.16/scalers/azure-data-explorer.md index 6493bafd1..787c05188 100644 --- a/content/docs/2.16/scalers/azure-data-explorer.md +++ b/content/docs/2.16/scalers/azure-data-explorer.md @@ -77,7 +77,7 @@ The AD identity that will be used requires `DatabaseViewer` role to query metric **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Examples @@ -144,7 +144,7 @@ metadata: name: azure-data-explorer-trigger-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.16/scalers/azure-event-hub.md b/content/docs/2.16/scalers/azure-event-hub.md index 926438526..cb1601cf3 100644 --- a/content/docs/2.16/scalers/azure-event-hub.md +++ b/content/docs/2.16/scalers/azure-event-hub.md @@ -80,7 +80,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ```yaml apiVersion: keda.sh/v1alpha1 @@ -90,7 +90,7 @@ metadata: namespace: default spec: podIdentity: - provider: Azure | azure-workload + provider: azure-workload ``` When you do so, the Event Hub scaler will depend on the existence of two configurations you have to provide: `eventHubNamespace` and `eventHubName`. You can also configure `storageAccountName` if you wish to use Azure AD Pod / Workload Identity to authenticate to Azure Blob Storage instead of a connection string. diff --git a/content/docs/2.16/scalers/azure-log-analytics.md b/content/docs/2.16/scalers/azure-log-analytics.md index c7743db27..26a75a522 100644 --- a/content/docs/2.16/scalers/azure-log-analytics.md +++ b/content/docs/2.16/scalers/azure-log-analytics.md @@ -152,7 +152,7 @@ You can use `TriggerAuthentication` CRD to configure the authentication by provi You can use managed identity to request access token for Log Analytics API. The advantage of this approach is that there is no need to store secrets in Kubernetes. Read [more](https://docs.microsoft.com/en-us/azure/aks/use-managed-identity) about managed identities in Azure Kubernetes Service. -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -248,7 +248,7 @@ metadata: namespace: kedaloganalytics spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.16/scalers/azure-monitor.md b/content/docs/2.16/scalers/azure-monitor.md index 156aa1099..330c583de 100644 --- a/content/docs/2.16/scalers/azure-monitor.md +++ b/content/docs/2.16/scalers/azure-monitor.md @@ -73,7 +73,7 @@ The user will need access to read data from the Azure resource. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -100,7 +100,7 @@ spec: key: activeDirectoryClientPassword # or Pod Identity, kind: Secret is not required in case of pod Identity podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.16/scalers/azure-pipelines.md b/content/docs/2.16/scalers/azure-pipelines.md index 3f8fa4373..cbb532b34 100644 --- a/content/docs/2.16/scalers/azure-pipelines.md +++ b/content/docs/2.16/scalers/azure-pipelines.md @@ -64,7 +64,7 @@ As an alternative to using environment variables, you can authenticate with Azur **Pod Identity Authentication** -[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### How to determine your pool ID diff --git a/content/docs/2.16/scalers/azure-service-bus.md b/content/docs/2.16/scalers/azure-service-bus.md index e7b9c6bf3..80873efbb 100644 --- a/content/docs/2.16/scalers/azure-service-bus.md +++ b/content/docs/2.16/scalers/azure-service-bus.md @@ -69,7 +69,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -82,7 +82,7 @@ metadata: name: azure-servicebus-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.16/scalers/azure-storage-blob.md b/content/docs/2.16/scalers/azure-storage-blob.md index 05bdbb220..1f895ad3b 100644 --- a/content/docs/2.16/scalers/azure-storage-blob.md +++ b/content/docs/2.16/scalers/azure-storage-blob.md @@ -56,7 +56,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod Identity Authentication** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. - `accountName` - Name of the Azure Storage Account. @@ -69,7 +69,7 @@ metadata: name: azure-blob-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.16/scalers/azure-storage-queue.md b/content/docs/2.16/scalers/azure-storage-queue.md index a95618537..ef55c5983 100644 --- a/content/docs/2.16/scalers/azure-storage-queue.md +++ b/content/docs/2.16/scalers/azure-storage-queue.md @@ -46,7 +46,7 @@ You can authenticate by using pod identity or connection string authentication. **Pod identity based authentication:** -[Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used. +[Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used. ### Example @@ -57,7 +57,7 @@ metadata: name: azure-queue-auth spec: podIdentity: - provider: azure | azure-workload + provider: azure-workload --- apiVersion: keda.sh/v1alpha1 kind: ScaledObject diff --git a/content/docs/2.16/scalers/prometheus.md b/content/docs/2.16/scalers/prometheus.md index a0750edd6..e72cf3668 100644 --- a/content/docs/2.16/scalers/prometheus.md +++ b/content/docs/2.16/scalers/prometheus.md @@ -87,7 +87,7 @@ To gain a better understanding of creating a Prometheus trigger for Amazon Manag #### Azure Monitor Managed Service for Prometheus Azure has a [managed service for Prometheus](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/prometheus-metrics-overview) and Prometheus scaler can be used to run prometheus query against that. -- [Azure AD Pod Identity](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity) or [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) providers can be used in `authenticationRef` - see later in example. +- [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/) provider can be used in `authenticationRef` - see later in example. - `Monitoring Data Reader` role needs to be assigned to workload identity (or pod identity) on the `Azure Monitor Workspace`. - No other auth (via `authModes`) can be provided with Azure Pod/Workload Identity Auth. - Prometheus query endpoint can be retreived from [Azure Monitor Workspace](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/azure-monitor-workspace-overview) that was configured to ingest prometheus metrics. @@ -406,7 +406,7 @@ metadata: name: azure-managed-prometheus-trigger-auth spec: podIdentity: - provider: azure | azure-workload # use "azure" for pod identity and "azure-workload" for workload identity + provider: azure-workload identityId: # Optional. Default: Identity linked with the label set when installing KEDA. --- apiVersion: keda.sh/v1alpha1