Merge pull request #84155 from SebastianSchuetze/patch-1

Added example on how to scale Azure Pipelines

Author: ktoliver

articles/container-apps/scale-app.md

@@ -198,6 +198,52 @@ The following example shows how to create a memory scaling rule.
 - In this example, the container app scales when memory usage exceeds 50%.
 - At a minimum, a single replica remains in memory for apps that scale based on memory utilization.
 
+## Azure Pipelines
+
+Azure Pipelines scaling allows your container app to scale in or out depending on the number of jobs in the Azure DevOps agent pool. With Azure Pipelines, your app can scale to zero, but you need [at least one agent registered in the pool schedule additional agents](https://keda.sh/blog/2021-05-27-azure-pipelines-scaler/). For more information regarding this scaler, see [KEDA Azure Pipelines scaler](https://keda.sh/docs/2.4/scalers/azure-pipelines/).
+
+The following example shows how to create a memory scaling rule.
+
+```json
+{
+  ...
+  "resources": {
+    ...
+    "properties": {
+      ...
+      "template": {
+        ...
+        "scale": {
+          "minReplicas": "0",
+          "maxReplicas": "10",
+          "rules": [{
+            "name": "azdo-agent-scaler",
+            "custom": {
+              "type": "azure-pipelines",
+              "metadata": {
+                  "poolID": "<pool id>",
+                  "targetPipelinesQueueLength": "1"
+              },
+              "auth": [
+                  {
+                      "secretRef": "<secret reference pat>",
+                      "triggerParameter": "personalAccessToken"
+                  },
+                  {
+                      "secretRef": "<secret reference Azure DevOps url>",
+                      "triggerParameter": "organizationURL"
+                  }
+              ]
+          }
+          }]
+        }
+      }
+    }
+  }
+}
+```
+
+In this example, the container app scales when at least one job is waiting in the pool queue.
 
 ## Considerations