Skip to content

Commit f965cfe

Browse files
authored
Merge pull request #124028 from JoeyC-Dev/patch-3
Fix format and update outdated API in ingress-controller-autoscale-pods.md
2 parents 1313f79 + c8b8809 commit f965cfe

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/application-gateway/ingress-controller-autoscale-pods.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,9 @@ Use following two components:
3030
1. First, create a Microsoft Entra service principal and assign it `Monitoring Reader` access over Application Gateway's resource group.
3131

3232
```azurecli
33-
applicationGatewayGroupName="<application-gateway-group-id>"
34-
applicationGatewayGroupId=$(az group show -g $applicationGatewayGroupName -o tsv --query "id")
35-
az ad sp create-for-rbac -n "azure-k8s-metric-adapter-sp" --role "Monitoring Reader" --scopes applicationGatewayGroupId
33+
applicationGatewayGroupName="<application-gateway-group-id>"
34+
applicationGatewayGroupId=$(az group show -g $applicationGatewayGroupName -o tsv --query "id")
35+
az ad sp create-for-rbac -n "azure-k8s-metric-adapter-sp" --role "Monitoring Reader" --scopes applicationGatewayGroupId
3636
```
3737
3838
1. Now, deploy the [`Azure Kubernetes Metric Adapter`](https://github.com/Azure/azure-k8s-metrics-adapter) using the Microsoft Entra service principal created previously.
@@ -98,7 +98,7 @@ In following example, we target a sample deployment `aspnet`. We scale up Pods w
9898

9999
Replace your target deployment name and apply the following auto scale configuration:
100100
```yaml
101-
apiVersion: autoscaling/v2beta1
101+
apiVersion: autoscaling/v2
102102
kind: HorizontalPodAutoscaler
103103
metadata:
104104
name: deployment-scaler

0 commit comments

Comments
 (0)