0

I have an IPv4 EKS cluster on AWS. My worker nodes have public IPv4 IPs.
AWS charges money for public IPv4s and I would like to get rid of them.
I also understand that I could use a NAT gateway with private IPv4s only for the worker nodes but the NAT Gateway also costs money.
When I tried to launch my nodes without public IPv4(but with public IPv6) and without a NAT gateway, the ec2 instances were created but they did not join the node group.
I suspect that EKS control plane APIs use IPv4 only.

Is there a way to setup an AWS EKS cluster without a NAT gateway and without public IPv4 for the worker nodes?

Improve this question

1 Answer 1

Reset to default
0

yes, check out https://fck-nat.dev/stable/, it works like charm

Improve this answer
1
  • While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review Commented Jun 10 at 15:48

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.