Fixing an Empty EKS Ingress Address by Deploying a Healthy ALB

A hands-on lab walks through turning a Kubernetes Ingress with an empty ADDRESS into a working internet-facing AWS Application Load Balancer on EKS. The Ingress stays unreconciled until the AWS Load Balancer Controller is installed with IAM permissions granted through EKS Pod Identity. Terraform provisions the VPC, tagged public subnets, EKS cluster, worker nodes, and controller IAM role, while a reproduction script deploys the app and Ingress beforehand. The author reports success with HTTP 200 responses, 2 of 2 healthy ALB targets, one successful reconciliation with no errors, and cluster metrics appearing in Splunk Observability Cloud. The full reproduce-and-fix run took about 28 minutes at an estimated cost under 1 USD.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in