Add metrics_server_resizer option (kubernetes-sigs#8018) (kubernetes-…

…sigs#8031)

The addon-resizer container can reduce resource limits of cpu and
memory of metrics-server container in the pod, and that caused
OOMKilled.
In addition, the original metrics-server manifest doesn't contain
the addon-resizer container as [1].
So this adds metrics_server_resizer option to control the addon-resizer
container deployment and the default value is false to make it stable
for most environments.

This is a cherry-pick of 8d3961e

[1]: https://github.com/kubernetes-sigs/metrics-server/blob/527679e5e8a103919c935d0575c20741796bc25d/manifests/base/deployment.yaml

roles/kubernetes-apps/metrics_server/defaults/main.yml

@@ -1,18 +1,9 @@
 ---
-# metrics_server_resizer only effective in arch amd64
-metrics_server_resizer: false
+metrics_server_container_port: 4443
 metrics_server_kubelet_insecure_tls: true
-metrics_server_kubelet_preferred_address_types: "InternalIP"
+metrics_server_kubelet_preferred_address_types: "InternalIP,ExternalIP,Hostname"
 metrics_server_metric_resolution: 15s
-metrics_server_cpu: 190m
-metrics_server_memory: 180Mi
-metrics_server_memory_per_node: 2Mi
-metrics_server_min_cluster_size: 10
 metrics_server_limits_cpu: 100m
 metrics_server_limits_memory: 200Mi
 metrics_server_requests_cpu: 100m
 metrics_server_requests_memory: 200Mi
-addon_resizer_limits_cpu: 40m
-addon_resizer_limits_memory: 25Mi
-addon_resizer_requests_cpu: 40m
-addon_resizer_requests_memory: 25Mi