Merge pull request #239162 from Nickomang/aks-keda-ga

KEDA GA

Author: denrea

articles/aks/includes/keda/current-version-callout.md

@@ -1,13 +1,14 @@
 ---
 author: tomkerkhove
-
 ms.service: azure-kubernetes-service
 ms.topic: include
-ms.date: 05/24/2022
+ms.date: 11/02/2023
 ms.author: tomkerkhove
 ---
 
 > [!IMPORTANT]
-> The KEDA add-on installs version *2.7.0* of KEDA on your cluster.
-> 
-> Due to [KEDA's Kubernetes Compatibility policy](https://keda.sh/docs/latest/operate/cluster/#kubernetes-compatibility), the managed KEDA addon is will only be supported in Kubernetes versions <= 1.25 when generally available. Please follow the [release notes](https://github.com/Azure/AKS/releases) to be notified for additional Kubernetes version support.
+> Your cluster Kubernetes version determines what KEDA version will be installed on your AKS cluster. To see which KEDA version maps to each AKS version, see the **AKS managed add-ons** column of the [Kubernetes component version table](/azure/aks/supported-kubernetes-versions#aks-components-breaking-changes-by-version). 
+>
+> For GA Kubernetes versions, AKS offers full support of the corresponding KEDA minor version in the table. Kubernetes preview versions and the latest KEDA patch are partially covered by customer support on a best-effort basis. As such, these features aren't meant for production use. For more information, see the following support articles:
+> - [AKS support policies](/azure/aks/support-policies)
+> - [Azure support FAQ](https://azure.microsoft.com/support/legal/faq/)

articles/aks/includes/keda/keda-workload-identity-callout.md

@@ -0,0 +1,17 @@
+---
+author: nickomang
+ms.service: azure-kubernetes-service
+ms.topic: include
+ms.date: 11/02/2023
+ms.author: nickoman
+---
+
+> [!NOTE]
+> If you're using [Microsoft Entra Workload ID](/azure/aks/workload-identity-overview) and you enable KEDA before Workload ID, you need to restart the KEDA operator pods so the proper environment variables can be injected:
+>
+> 1. Restart the pods by running `kubectl rollout restart deployment keda-operator -n kube-system`.
+>
+> 1. Obtain KEDA operator pods using `kubectl get pod -n kube-system` and finding pods that begin with `keda-operator`.
+>
+> 1. Verify successful injection of the environment variables by running `kubectl describe pod <keda-operator-pod> -n kube-system`.
+> Under `Environment`, you should see values for `AZURE_TENANT_ID`, `AZURE_FEDERATED_TOKEN_FILE`, and `AZURE_AUTHORITY_HOST`.

articles/aks/keda-about.md

@@ -1,21 +1,19 @@
 ---
-title: Kubernetes Event-driven Autoscaling (KEDA) (Preview)
+title: Kubernetes Event-driven Autoscaling (KEDA)
 description: Simplified application autoscaling with Kubernetes Event-driven Autoscaling (KEDA) add-on.
 author: tomkerkhove
 ms.topic: article
-ms.date: 06/06/2023
+ms.date: 08/08/2023
 ms.author: tomkerkhove
 ---
 
-# Simplified application autoscaling with Kubernetes Event-driven Autoscaling (KEDA) add-on (Preview)
+# Simplified application autoscaling with Kubernetes Event-driven Autoscaling (KEDA) add-on
 
 Kubernetes Event-driven Autoscaling (KEDA) is a single-purpose and lightweight component that strives to make application autoscaling simple and is a CNCF Graduate project.
 
 It applies event-driven autoscaling to scale your application to meet demand in a sustainable and cost-efficient manner with scale-to-zero.
 
-The KEDA add-on makes it even easier by deploying a managed KEDA installation, providing you with [a rich catalog of 50+ KEDA scalers][keda-scalers] that you can scale your applications with on your Azure Kubernetes Services (AKS) cluster.
-
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
+The KEDA add-on makes it even easier by deploying a managed KEDA installation, providing you with [a rich catalog of Azure KEDA scalers][keda-scalers] that you can scale your applications with on your Azure Kubernetes Services (AKS) cluster.
 
 ## Architecture
 
@@ -28,7 +26,7 @@ The KEDA add-on makes it even easier by deploying a managed KEDA installation, p
 
 Learn more about how KEDA works in the [official KEDA documentation][keda-architecture].
 
-## Installation and version
+## Installation
 
 KEDA can be added to your Azure Kubernetes Service (AKS) cluster by enabling the KEDA add-on using an [ARM template][keda-arm] or [Azure CLI][keda-cli].
 
@@ -39,11 +37,15 @@ The KEDA add-on provides a fully supported installation of KEDA that is integrat
 KEDA provides the following capabilities and features:
 
 - Build sustainable and cost-efficient applications with scale-to-zero
-- Scale application workloads to meet demand using [a rich catalog of 50+ KEDA scalers][keda-scalers]
+- Scale application workloads to meet demand using [a rich catalog of Azure KEDA scalers][keda-scalers]
 - Autoscale applications with `ScaledObjects`, such as Deployments, StatefulSets or any custom resource that defines `/scale` subresource
 - Autoscale job-like workloads with `ScaledJobs`
 - Use production-grade security by decoupling autoscaling authentication from workloads
 - Bring-your-own external scaler to use tailor-made autoscaling decisions
+- Integrate with [Microsoft Entra Workload ID][workload-identity] for authentication
+
+> [!NOTE]
+> If you plan to use workload identity, [enable the workload identity add-on][workload-identity-deploy] before enabling the KEDA add-on.
 
 ## Add-on limitations
 
@@ -53,22 +55,36 @@ The KEDA AKS add-on has the following limitations:
 * KEDA's [external scaler for Azure Cosmos DB][keda-cosmos-db-scaler] to scale based on Azure Cosmos DB change feed isn't installed with the extension, but can be deployed separately.
 * Only one metric server is allowed in the Kubernetes cluster. Because of that the KEDA add-on should be the only metrics server inside the cluster.
     * Multiple KEDA installations aren't supported
-* Managed identity isn't supported.
 
 For general KEDA questions, we recommend [visiting the FAQ overview][keda-faq].
 
+[!INCLUDE [Current version callout](./includes/keda/keda-workload-identity-callout.md)]
+
+## Supported Kubernetes and KEDA versions
+
+Your cluster Kubernetes version determines what KEDA version will be installed on your AKS cluster. To see which KEDA version maps to each AKS version, see the **AKS managed add-ons** column of the [Kubernetes component version table](./supported-kubernetes-versions.md#aks-components-breaking-changes-by-version). 
+
+For GA Kubernetes versions, AKS offers full support of the corresponding KEDA minor version in the table. Kubernetes preview versions and the latest KEDA patch are partially covered by customer support on a best-effort basis. As such, these features aren't meant for production use. For more information, see the following support articles:
+
+- [AKS support policies][support-policies]
+- [Azure support FAQ][azure-support-faq]
+
 ## Next steps
 
 * [Enable the KEDA add-on with an ARM template][keda-arm]
 * [Enable the KEDA add-on with the Azure CLI][keda-cli]
 * [Troubleshoot KEDA add-on problems][keda-troubleshoot]
 * [Autoscale a .NET Core worker processing Azure Service Bus Queue messages][keda-sample]
+* [View the upstream KEDA docs][keda]
 
 <!-- LINKS - internal -->
 [keda-azure-cli]: keda-deploy-addon-az-cli.md
 [keda-cli]: keda-deploy-add-on-cli.md
 [keda-arm]: keda-deploy-add-on-arm.md
 [keda-troubleshoot]: /troubleshoot/azure/azure-kubernetes/troubleshoot-kubernetes-event-driven-autoscaling-add-on?context=/azure/aks/context/aks-context
+[workload-identity]: ./workload-identity-overview.md
+[workload-identity-deploy]: ./workload-identity-deploy-cluster.md
+[support-policies]: ./support-policies.md
 
 <!-- LINKS - external -->
 [keda]: https://keda.sh/
@@ -78,3 +94,4 @@ For general KEDA questions, we recommend [visiting the FAQ overview][keda-faq].
 [keda-scalers]: https://keda.sh/docs/scalers/
 [keda-http-add-on]: https://github.com/kedacore/http-add-on
 [keda-cosmos-db-scaler]: https://github.com/kedacore/external-scaler-azure-cosmos-db
+[azure-support-faq]: https://azure.microsoft.com/support/legal/faq/

articles/aks/keda-deploy-add-on-arm.md

@@ -1,11 +1,11 @@
 ---
 title: Install the Kubernetes Event-driven Autoscaling (KEDA) add-on using an ARM template
 description: Use an ARM template to deploy the Kubernetes Event-driven Autoscaling (KEDA) add-on to Azure Kubernetes Service (AKS).
-author: jahabibi
+author: nickomang
 ms.topic: article
 ms.custom: devx-track-azurecli, devx-track-arm-template
 ms.date: 09/26/2023
-ms.author: jahabibi
+ms.author: nickoman
 ---
 
 # Install the Kubernetes Event-driven Autoscaling (KEDA) add-on using an ARM template
@@ -20,49 +20,11 @@ This article shows you how to deploy the Kubernetes Event-driven Autoscaling (KE
 - You need the [Azure CLI installed](/cli/azure/install-azure-cli).
 - This article assumes you have an existing Azure resource group. If you don't have an existing resource group, you can create one using the [`az group create`][az-group-create] command.
 - Ensure you have firewall rules configured to allow access to the Kubernetes API server. For more information, see [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters][aks-firewall-requirements].
-- [Install the `aks-preview` Azure CLI extension](#install-the-aks-preview-azure-cli-extension).
-- [Register the `AKS-KedaPreview` feature flag](#register-the-aks-kedapreview-feature-flag).
 - [Create an SSH key pair](#create-an-ssh-key-pair).
 
-### Install the `aks-preview` Azure CLI extension
+[!INCLUDE [KEDA workload ID callout](./includes/keda/keda-workload-identity-callout.md)]
 
-[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
-
-1. Install the `aks-preview` extension using the [`az extension add`][az-extension-add] command.
-
-    ```azurecli-interactive
-    az extension add --name aks-preview
-    ```
-
-2. Update to the latest version of the `aks-preview` extension using the [`az extension update`][az-extension-update] command.
-
-    ```azurecli-interactive
-    az extension update --name aks-preview
-    ```
-
-### Register the `AKS-KedaPreview` feature flag
-
-1. Register the `AKS-KedaPreview` feature flag using the [`az feature register`][az-feature-register] command.
-
-    ```azurecli-interactive
-    az feature register --namespace "Microsoft.ContainerService" --name "AKS-KedaPreview"
-    ```
-
-    It takes a few minutes for the status to show *Registered*.
-
-2. Verify the registration status using the [`az feature show`][az-feature-show] command.
-
-    ```azurecli-interactive
-    az feature show --namespace "Microsoft.ContainerService" --name "AKS-KedaPreview"
-    ```
-
-3. When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider using the [`az provider register`][az-provider-register] command.
-
-    ```azurecli-interactive
-    az provider register --namespace Microsoft.ContainerService
-    ```
-
-### Create an SSH key pair
+## Create an SSH key pair
 
 1. Navigate to the [Azure Cloud Shell](https://shell.azure.com/).
 2. Create an SSH key pair using the [`az sshkey create`][az-sshkey-create] command.
@@ -104,11 +66,65 @@ To connect to the Kubernetes cluster from your local device, you use [kubectl][k
 
 If you use the Azure Cloud Shell, `kubectl` is already installed. You can also install it locally using the [`az aks install-cli`][az-aks-install-cli] command.
 
-- Configure `kubectl` to connect to your Kubernetes cluster using the [`az aks get-credentials`][az-aks-get-credentials] command.
-
-    ```azurecli-interactive
-    az aks get-credentials --resource-group <resource-group-name> --name <cluster-name>
-    ```
+- Configure `kubectl` to connect to your Kubernetes cluster, use the [az aks get-credentials][az-aks-get-credentials] command. The following example gets credentials for the AKS cluster named *MyAKSCluster* in the *MyResourceGroup*:
+
+```azurecli
+az aks get-credentials --resource-group MyResourceGroup --name MyAKSCluster
+```
+
+## Example deployment
+
+The following snippet is a sample deployment that creates a cluster with KEDA enabled with a single node pool comprised of three `DS2_v5` nodes.
+
+```json
+{
+    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+    "contentVersion": "1.0.0.0",
+    "resources": [
+        {
+            "apiVersion": "2023-03-01",
+            "dependsOn": [],
+            "type": "Microsoft.ContainerService/managedClusters",
+            "location": "westcentralus",
+            "name": "myAKSCluster",
+            "properties": {
+                "kubernetesVersion": "1.27",
+                "enableRBAC": true,
+                "dnsPrefix": "myAKSCluster",
+                "agentPoolProfiles": [
+                    {
+                        "name": "agentpool",
+                        "osDiskSizeGB": 200,
+                        "count": 3,
+                        "enableAutoScaling": false,
+                        "vmSize": "Standard_D2S_v5",
+                        "osType": "Linux",
+                        "storageProfile": "ManagedDisks",
+                        "type": "VirtualMachineScaleSets",
+                        "mode": "System",
+                        "maxPods": 110,
+                        "availabilityZones": [],
+                        "nodeTaints": [],
+                        "enableNodePublicIP": false
+                    }
+                ],
+                "networkProfile": {
+                    "loadBalancerSku": "standard",
+                    "networkPlugin": "kubenet"
+                },
+                "workloadAutoScalerProfile": {
+                    "keda": {
+                        "enabled": true
+                    }
+                }
+            },
+            "identity": {
+                "type": "SystemAssigned"
+            }
+        }
+    ]
+}
+```
 
 ## Start scaling apps with KEDA
 
@@ -128,6 +144,8 @@ This article showed you how to install the KEDA add-on on an AKS cluster, and th
 
 For information on KEDA troubleshooting, see [Troubleshoot the Kubernetes Event-driven Autoscaling (KEDA) add-on][keda-troubleshoot].
 
+To learn more, view the [upstream KEDA docs][keda].
+
 <!-- LINKS - internal -->
 [az-group-delete]: /cli/azure/group#az-group-delete
 [keda-troubleshoot]: /troubleshoot/azure/azure-kubernetes/troubleshoot-kubernetes-event-driven-autoscaling-add-on?context=/azure/aks/context/aks-context
@@ -146,3 +164,4 @@ For information on KEDA troubleshooting, see [Troubleshoot the Kubernetes Event-
 [kubectl]: https://kubernetes.io/docs/reference/kubectl/
 [keda-scalers]: https://keda.sh/docs/scalers/
 [keda-sample]: https://github.com/kedacore/sample-dotnet-worker-servicebus-queue
+[keda]: https://keda.sh/docs/2.12/