You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/use-metrics-server-vertical-pod-autoscaler.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ AKS cluster is running Kubernetes version 1.24 and higher.
17
17
18
18
## Metrics server crashloopbackoff or throttling
19
19
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.
21
21
22
22
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.
23
23
@@ -82,7 +82,7 @@ Be cautious of the *baseCPU*, *cpuPerNode*, *baseMemory*, and the *memoryPerNode
82
82
83
83
## Manually configure Metrics Server resource usage
84
84
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.
86
86
87
87
If you would like to bypass VPA for Metrics Server and manually control its resource usage, perform the following steps.
88
88
@@ -147,7 +147,7 @@ If you would like to bypass VPA for Metrics Server and manually control its reso
147
147
148
148
## Troubleshooting
149
149
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`.
0 commit comments