Amshuman K R

> use a separate controller that keeps track of the Gardener metrics endpoint and scale it down to 0 if the metrics indicate an issue with the new Gardener version...

/assign @harishmanasa

> By the way, metrics server cannot benefit from horizontal scaling as each replica always scrape all pods and nodes resource usage, see kubernetes-sigs/metrics-server#552 for more details. Thanks! This is...

> One thing to keep in mind with this approach is that the metrics-server constantly talks to all kubelets. By moving it to the Seed, we would cause some constant...

Thanks a lot for the suggestions and for reaching out @serathius! The confirmation about the approach of using `addon-resizer` for MS is reassuring :-) > Official repo already has alternative...

While testing the changes in gardener to use the `addon-resizer`, we found that there is a race between the `gardener-resource-manager` and the `addon-resizer` in updating the `metrics-server`. The `metrics-server` keeps...

I think we should also look at the number of goroutines and retry logic. But let's profile first.

@majst01 #341 addressed the constant increase in CPU usage. Does it not work for you? We have kept the current issue open to track the optimisation of the baseline CPU...

> We already have #341 Thanks. We saw improvement with #341. But this is good information for us. We will also check from our end.

> I doubt that the changes upstream since #341 change any behavior here. Yes. If you already have #341, there are no further relevant changes that might help.