AWS EKS - Create Load Balancer Service throws out of service

7
votes

I have a quick question regarding AWS EKS that whenever I create a K8s service with of type LoadBalancer, it provisions a classic ELB backed the EC2 where services are running. Now whenever I try to hit the Load Balancer ELB from the Internet, it returns ERR_EMPTY_RESPONSE error. If I navigate back to ELB and look at the instances behind ELB, it shows the status of EC2 instances as OutOfService.

This happens either I use my own K8s deployments & services or the one provided with documentation. Anyone can help me with this? More over, is there any way to provision a different type of Load Balancer for a K8s service? Thanks.

1
amazon-web-servicesdockerkubernetes
I have the same issue. – Younghan
I have created my EKS cluster with terraform. On that cluster, I had this issue. But when I created a cluster with docs.aws.amazon.com/eks/latest/userguide/getting-started.html manually, it works with no issue. – Younghan
Same here. I followed the same steps mentioned in the documentation on Terraform website for EKS and it worked. It seems like we're missing the tag name (EKS Cluster Name) assign to the subnet in the Terraform configuration file. – Janshair Khan
After deleting some load balancer services and applying them again, ELB health checks failed again on the cluster which was created manually (i.e. without terraform) – Younghan
I'm working for creating a Terraform Module for EKS. I'll update on the registry when it's ready. – Janshair Khan

1 Answers

-3
votes

This is default behavior or K8S with on cloud providers , A service type Load Balancer will spins up real one which affect cost. Better to use K8S Ingress as best practice and can use as Endpoint or you can add under External Load Balancer.