Skip to content

How to verify and configure private EKS Worker nodes' internet connectivity?

0

Hi,

I have an EKS cluster deployed in a VPC with 3x private subnets and 3x public subnets. My worker nodes are EKS Managed nodes running Bottlerocket, and these are deployed in the private subnets. I use the Terraform EKS module for this.

To give some more details about my network: The public subnet has a single NAT GW, and there is also an INET GW. I have a route table which associates the private subnets with the NAT GW for outbound access, and the public subnets to the INET GW. I have also deployed an ingress NGINX controller in my cluster, which has created an NLB on the public subnet for ingress purposes. My NACLs are fine, with 100 priority on all outbound and inbound from 0.0.0.0/0 in the VPC. Security groups associated with my worker nodes also allow all outbound traffic.

I have deployed Cilium in my network and configured it to be in chaining mode with the VPC-CNI add-on. I also have CoreDNS and kube-proxy installed.

Whilst DNS works from my Pods, it seems I cannot connect to sites outside my VPC. The reason I am asking this question is because my ArgoCD repo-server is timing out when connecting to my GitHub repository. I tried curling github.com from my pods, and the requests time out, so it seems something is off in my network, but I am not sure what. Been stuck on this for a couple of days so hoping to get some help!

  • Can you share your Terrafrom c o d e?

3 Answers
0

I would start by using VPC Reachability Analyzer - it will mathematically (no packets required!) tell you if X can talk to Y (where X can be EKS and Y can be the internet). From there, the tool can tell you what is blocking the traffic. If nothing is then it will be something inside the worker nodes.

EXPERT

answered 2 years ago

0

Hello,

Welcome to AWS re:Post!

I understand you are facing connectivity issues to sites outside the VPC from the pods.

Going through the issue, I would suggest using VPC Reachability Analyzer - it will mathematically (no packets required!) tell you if A can talk to B (where A can be EKS and B can be the internet). From there, the tool can tell you what is blocking the traffic and If nothing is then it will be something inside the worker nodes.

Moreover, I would suggest you to reach out to our EKS team via a support case in order to get the exact guidance regarding the issue!

AWS
SUPPORT ENGINEER

answered 2 years ago

0

Hi,

After re-building my environment and avoiding the Cilium VPC in chaining mode, I seem to have resolved this. Thanks for suggesting the above solutions.

Best, Mattia

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.