I just started using the provider (version 1.26.0-alpha.1) with a basic configuration but I'm having trouble with the metrics-server. It fails to scrape node metrics with the error message:
E0906 16:54:20.683294 1 scraper.go:140] "Failed to scrape node" err="Get \"https://i-04cb08573c1656c4f.ec2.internal:10250/metrics/resource\": dial tcp: lookup i-04cb08573c1656c4f.ec2.internal on 100.64.0.10:53: no such host" node="i-04cb08573c1656c4f"
I found this workaround where I had to manually edit the metrics-server deployment and add the --kubelet-preferred-address-types=InternalIP arg and it worked, but I wanted it to be configured on cluster startup. Is it possible to add an input variable in the metrics_server_config in order to allow custom args? Or is there an easier solution that I'm missing?
I'm running a single control-plane node with two worker nodes on AWS. My current cluster config is looking like this:
I just started using the provider (version
1.26.0-alpha.1
) with a basic configuration but I'm having trouble with the metrics-server. It fails to scrape node metrics with the error message:I found this workaround where I had to manually edit the
metrics-server
deployment and add the--kubelet-preferred-address-types=InternalIP
arg and it worked, but I wanted it to be configured on cluster startup. Is it possible to add an input variable in themetrics_server_config
in order to allow custom args? Or is there an easier solution that I'm missing?I'm running a single control-plane node with two worker nodes on AWS. My current cluster config is looking like this: