Aws-load-balancer-controller: Connection Refused when testing example

Created on 20 Aug 2020  路  3Comments  路  Source: kubernetes-sigs/aws-load-balancer-controller

Hello, my company is looking at using EKS + Fargate for our new architecture. I have set up an EKS cluster without any issues using:
https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html

I have now been following this example using Fargate profiles: https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html

Everything seems to work until I get to the end and get the following when looking at the logs for the alb-ingress-controller:

E0820 13:24:27.546562       1 controller.go:217] kubebuilder/controller "msg"="Reconciler error" "error"="failed to build LoadBalancer configuration due to unable to fetch subnets. Error: WebIdentityErr: failed to retrieve credentials\ncaused by: RequestError: send request failed\ncaused by: Post https://sts.eu-west-1.amazonaws.com/: dial tcp: lookup sts.eu-west-1.amazonaws.com on 10.100.0.10:53: read udp 192.168.255.60:60566-\u003e10.100.0.10:53: i/o timeout"  "controller"="alb-ingress-controller" "request"={"Namespace":"2048-game","Name":"2048-ingress"}
E0820 13:27:46.375207       1 request_pagination.go:107] Failed request: ec2/DescribeSubnets, Payload: {  Filters: [{      Name: "tag:kubernetes.io/cluster/testEKSCluster",      Values: ["owned","shared"]    },{      Name: "tag:kubernetes.io/role/elb",      Values: ["","1"]    }]}, Error: WebIdentityErr: failed to retrieve credentials
caused by: RequestError: send request failed
caused by: Post https://sts.eu-west-1.amazonaws.com/: dial tcp: lookup sts.eu-west-1.amazonaws.com on 10.100.0.10:53: read udp 192.168.255.60:57652->10.100.0.10:53: read: connection refused
E0820 13:27:46.375473       1 controller.go:217] kubebuilder/controller "msg"="Reconciler error" "error"="failed to build LoadBalancer configuration due to unable to fetch subnets. Error: WebIdentityErr: failed to retrieve credentials\ncaused by: RequestError: send request failed\ncaused by: Post https://sts.eu-west-1.amazonaws.com/: dial tcp: lookup sts.eu-west-1.amazonaws.com on 10.100.0.10:53: read udp 192.168.255.60:57652-\u003e10.100.0.10:53: read: connection refused"  "controller"="alb-ingress-controller" "request"={"Namespace":"2048-game","Name":"2048-ingress"}
E0820 13:31:07.710653       1 request_pagination.go:107] Failed request: ec2/DescribeSubnets, Payload: {  Filters: [{      Name: "tag:kubernetes.io/cluster/testEKSCluster",      Values: ["owned","shared"]    },{      Name: "tag:kubernetes.io/role/elb",      Values: ["","1"]    }]}, Error: WebIdentityErr: failed to retrieve credentials
caused by: RequestError: send request failed
caused by: Post https://sts.eu-west-1.amazonaws.com/: dial tcp: lookup sts.eu-west-1.amazonaws.com on 10.100.0.10:53: read udp 192.168.255.60:33769->10.100.0.10:53: i/o timeout
E0820 13:31:07.710902       1 controller.go:217] kubebuilder/controller "msg"="Reconciler error" "error"="failed to build LoadBalancer configuration due to unable to fetch subnets. Error: WebIdentityErr: failed to retrieve credentials\ncaused by: RequestError: send request failed\ncaused by: Post https://sts.eu-west-1.amazonaws.com/: dial tcp: lookup sts.eu-west-1.amazonaws.com on 10.100.0.10:53: read udp 192.168.255.60:33769-\u003e10.100.0.10:53: i/o timeout"  "controller"="alb-ingress-controller" "request"={"Namespace":"2048-game","Name":"2048-ingress"}

I have deleted everything and started from scratch multiple times and this is what I get each time. Can anyone help?

Most helpful comment

Hi, seems your coreDNS setup is not correct.
Have you configured coreDNS to run on fargate? refer: https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html

All 3 comments

Hi, seems your coreDNS setup is not correct.
Have you configured coreDNS to run on fargate? refer: https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html

@NickEAVE did above recommendation solves your issue?
feel free to reopen if it don't work.

I was able to fix "connection refused" error by following the link provided by @M00nF1sh in order to setup coreDNS properly , thanks a lot :fireworks: . Greetings from :mexico:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sawanoboly picture sawanoboly  路  5Comments

jchoi926 picture jchoi926  路  3Comments

mgoodness picture mgoodness  路  5Comments

gigi-at-zymergen picture gigi-at-zymergen  路  5Comments

amalagaura picture amalagaura  路  4Comments