Closed adriananeci closed 5 years ago
@Etiene Could you review this one?
Thanks for the PR! I'm going to kickoff our current automated tests, but how did you test this?
@Etiene It was manually tested, didn't write any unit tests.
Seems to be a routing issue based on the tests output:
TestConsulClusterWithAmazonLinuxAmi 2019-05-22T11:41:48Z retry.go:75: Check Consul members returned an error: Get http://15.164.93.172:8500/v1/agent/members: dial tcp 15.164.93.172:8500: getsockopt: no route to host. Sleeping for 10s and will try again.
Could you please rebase your PR now that a fix has been issued?
Thank you! :)
In order to be able to add recursors servers to consul config (https://www.consul.io/docs/agent/options.html#recursors) a new parameter needs to be added to run-consul script. It is useful when you also install dnsmasq and want to recursively resolve queries that are not inside the consul service domain. Another example could be if you want to access a private EKS API endpoint from an on-premise network connected through AWS Direct Connect (DX) or a virtual private network (VPN) to EKS VPC.