EKS Master Node is unreachable on existing VPC but works perfectly fine on any other vpc

Viewed 26

I'm basically trying to spin up EKS using Terraform on my VPC which is having a CIDR of 10.0.0.0/16. When defining the EKS through terraform, I'm also defining the K8's network config and assigning it a CIDR of 172.16.0.0/12 . But the issue is that it creates the cluster though but nodegroups are unable to join the cluster and also I'm not able to issue kubectl commands from my terminal as it gets timeout error.

But if I try everything same with any other VPC, everything works perfectly fine. Is it because of my VPC CIDR clashing with k8's CIDR ? I read terraform EKS documentation and it said that k8 is assigned a default CIDR from one of these CIDRS : 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16.

When EKS gets created and when i check it through the console, it shows K8 CIDR is the same which i have passed it i.e 172.16.0.0/12 . I'm just not sure what exactly the issue is. DNS support is also enabled. We have many other resources in same VPC so we dont really want a new VPC for this and want to deploy EKS on this VPC of CIDR 10.0.0.0/16 .

Using Kubernetes version 1.22.

Can anyone help with this ?

0 Answers
Related