Skip to content

Commit 30635bb

Browse files
committed
Fixed grammar
1 parent 98b63de commit 30635bb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/aks/use-metrics-server-vertical-pod-autoscaler.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ AKS cluster is running Kubernetes version 1.24 and higher.
1717

1818
## Metrics server crashloopbackoff or throttling
1919

20-
If the Metrics Server throttling rate is high, and the memory usage of its two pods are unbalanced, this indicates the Metrics Server requires more resources than the default values specified.
20+
If the Metrics Server throttling rate is high, and the memory usage of its two pods is unbalanced, this indicates the Metrics Server requires more resources than the default values specified.
2121

2222
To update the coefficient values, create a ConfigMap in the overlay *kube-system* namespace to override the values in the Metrics Server specification. Perform the following steps to update the metrics server.
2323

@@ -82,7 +82,7 @@ Be cautious of the *baseCPU*, *cpuPerNode*, *baseMemory*, and the *memoryPerNode
8282

8383
## Manually configure Metrics Server resource usage
8484

85-
The Metrics Server VPA adjusts resource usage by the number of nodes. If the cluster scale up or down often, the Metrics Server might restart frequently. In this case, you can bypass VPA and manually control its resource usage. This method to configure VPA isn't to be performed in addition to the steps described in the previous section.
85+
The Metrics Server VPA adjusts resource usage by the number of nodes. If the cluster scales up or down often, the Metrics Server might restart frequently. In this case, you can bypass VPA and manually control its resource usage. This method to configure VPA isn't to be performed in addition to the steps described in the previous section.
8686

8787
If you would like to bypass VPA for Metrics Server and manually control its resource usage, perform the following steps.
8888

@@ -147,7 +147,7 @@ If you would like to bypass VPA for Metrics Server and manually control its reso
147147

148148
## Troubleshooting
149149

150-
1. If you use the following configmap, the Metrics Server VPA customization aren't applied. You need add a unit for `baseCPU`.
150+
1. If you use the following configmap, the Metrics Server VPA customizations aren't applied. You need add a unit for `baseCPU`.
151151

152152
```yml
153153
apiVersion: v1

0 commit comments

Comments
 (0)