Integrate KEDA with your Azure Kubernetes Service cluster

Kubernetes-based Event Driven Autoscaler (KEDA) lets you drive the scaling of any container in Kubernetes based on the load to be processed, by querying metrics from systems such as Prometheus.

Azure Kubernetes Service (AKS) supports integration of KEDA with your AKS cluster to scale your workloads based on Azure Monitor managed service for Prometheus metrics from your Azure Monitor workspace.

Azure Monitor managed service for Prometheus (also known as Managed Prometheus in Azure) is a fully managed Prometheus service in Azure (it includes a fully managed data store, query service, ruler service, Prometheus compatible query APIs, and managed add-on for data collection from, ARC-connected on-prem or other cloud Kubernetes offerings). As a first step, this service is fully integrated with Azure Kubernetes Service (AKS) as an add-on which scrapes Prometheus metrics.

To integrate KEDA into your Azure Kubernetes Service, you will need to deploy and configure a workload identity or pod identity on your cluster. This identity allows KEDA to authenticate with Azure and retrieve metrics for scaling from your Monitor workspace.

We recommend using Azure Active Directory workload identity. This authentication method replaces pod-managed identity (pod-managed identity in AKS has been deprecated as of 10/24/2022), which integrates with the Kubernetes native capabilities to federate with any external identity providers on behalf of the application.

Azure Managed Prometheus support starts from KEDA v2.10. If you have an older version of KEDA installed, you must upgrade in order to work with Azure Managed Prometheus.

To integrate KEDA into your AKS, please start with our documentation, and reach out to us should you have any feedback or questions!

Continue reading...