End-to-end GitOps With Terraform and ArgoCD For EKS

Your Current Load Balancers:

1. frontend application CLB (

   a6b4f060d89f045899d8e45accbb683c

   ):

   • Handles traffic on port 3000 → routes to port 30604 on your worker nodes

   • Likely for a specific application or service

2. argocd server CLB (

   a00a7bc4c045a4c759d2b1d5aba7d68a

   ):

   • Handles HTTP (port 80) → routes to port 31209 on your worker nodes

   • Handles HTTPS (port 443) → routes to port 32218 on your worker nodes

   • Likely for web traffic (HTTP/HTTPS)

1. Web Application Load Balancer: This handles standard web traffic (HTTP/HTTPS)

2. SSL/TLS Support: Port 443 suggests HTTPS/SSL termination

3. Kubernetes-Managed: The k8s-elb- prefix indicates it was created by a Kubernetes service

4. Different from Frontend LB: This serves different ports (31209/32218) compared to your frontend app (30604)

Traffic Flow:

Detailed Breakdown:

1. User Request:

   • User accesses: http://load-balancer-url:3000

2. Load Balancer (Public Subnets):

   • Receives traffic on port 3000

   • Routes to worker nodes on port 30604 (NodePort)

3. Worker Nodes (Private Subnets):

   • EKS worker nodes (i-05093d891e8a8b3a7, i-0e7e1f91d1e7f9d04)

   • Located in private subnets (10.0.1.0/24, 10.0.2.0/24)

   • NodePort service listens on port 30604

4. Kubernetes Service (NodePort):

   • Routes traffic from NodePort 30604 to frontend pods

   • Typically forwards to pod port 3000 or 8080 (depends on your app)

5. Frontend Pod:

   • Contains your frontend application (React, Angular, etc.)

   • Serves the actual web application

29/30 - End-to-end GitOps With Terraform and ArgoCD For EKS | Production-grade Kubernetes Project