metrics-server: [EKS] unable to fetch metrics from Kubelet

Hi,

I am testing the recently released HPA on Amazon’s EKS but running into an issue where it’s failing to ping the node.

(actual IP redacted)

$ kubectl logs -l app=metrics-server -n kube-system
...
E0901 04:09:10.815694       1 manager.go:102] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:ip-aa-bb-cc-dd.ec2.internal: unable to fetch metrics from Kubelet ip-aa-bb-cc-dd.ec2.internal (ip-aa-bb-cc-dd.ec2.internal): Get https://ip-aa-bb-cc-dd.ec2.internal:10250/stats/summary/: dial tcp: lookup ip-aa-bb-cc-dd.ec2.internal on 10.100.0.10:53: no such host, unable to fully scrape metrics from source 
$ kubectl get nodes
NAME                             STATUS    ROLES     AGE       VERSION
ip-aa-bb-cc-dd.ec2.internal   Ready     <none>    1h        v1.10.3
$ kubectl describe node 
...
Addresses:
  InternalIP:  aa.bb.cc.dd
  Hostname:    ip-aa-bb-cc-dd.ec2.internal

I am using v0.3 after running kubectl apply -f metrics-server/deploy/1.8+/ on commit 931ef8402ac7e9545156041e4479a02b055c0ab4

Do i need to configure something?

Thanks

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 1
  • Comments: 20 (2 by maintainers)

Commits related to this issue

Most upvoted comments

The solution proposed by @MIBc works. Change the metrics-server-deployment.yaml file and add:

command: - /metrics-server - --kubelet-preferred-address-types=InternalIP

Figured out my issue – my worker node security group was misconfigured. I had to add an inbound rule to allow HTTPS (port 443) traffic from the control plane security group.

I just added incoming 443 from CONTROLE PLANE SECURITY GROUP and looks like it’s working now. Thanks @sc-rz

Nevermind, this was an issue with my VPC DNS resolution