<p>I noticed some of my clusters were reporting a CPUThrottlingHigh alert for metrics-server-nanny container (image: gke.gcr.io/addon-resizer:1.8.11-gke.0) in GKE.  I couldn't see a way to configure this container to give it more CPU because it's automatically deployed as part of the metrics-server pod, and Google automatically resets any changes to the deployment/pod resource settings.</p>
<p>So out of curiosity, I created a small kubernetes cluster in GKE (3 standard nodes) with autoscaling turned on to scale up to 5 nodes.  No apps or anything installed.  Then I installed the kube-prometheus monitoring stack (<a href="https://github.com/prometheus-operator/kube-prometheus" rel="nofollow noreferrer">https://github.com/prometheus-operator/kube-prometheus</a>) which includes the CPUThrottlingHigh alert.  Soon after installing the monitoring stack, this same alert popped up for this container.  I don't see anything in the logs of this container or the related metrics-server-nanny container.</p>
<p>Also, I don't notice this same issue on AWS or Azure because while they do have a similar metrics-server pod in the kube-system namespace, they do not contain the sidecar metrics-server-nanny container in the pod.</p>
<p>Has anyone seen this or something similar?  Is there a way to give this thing more resources without Google overwriting config changes?</p>

<p><a href="https://github.com/robusta-dev/alert-explanations/wiki/CPUThrottlingHigh-on-metrics-server-(Prometheus-alert)" rel="nofollow noreferrer">This is a known issue with GKE metrics-server.</a></p>
<p>You can't fix the error on GKE as GKE controls the metric-server configuration and any changes you make are reverted.</p>
<p><a href="https://github.com/robusta-dev/alert-explanations/wiki/CPUThrottlingHigh-on-metrics-server-(Prometheus-alert)#recommended-remediation-for-gke-clusters" rel="nofollow noreferrer">You should silence the alert on GKE</a> or update to a GKE cluster version that fixes this.</p>
