How the AWS Load Balancer Controller Works

How the AWS Load Balancer Controller Works A sequence diagram generated by Archify. Create Ingress / Service Watch event Request Load Balancer creation Called after analyzing the resource (annotations · spec) Provision ALB / NLB Return ARN Create Target Group Configure Listener rules Update Status Provide Load Balancer DNS Auto-register / deregister targets 1. Detect resource 2. Provision AWS resources 3. Return result 4. Ongoing reconciliation (on Pod changes) User · kubectl apply · Sequence participant User kubectl apply Kubernetes API · Ingress / Service · Sequence participant Kubernetes API Ingress / Service LB Controller · kube-system · Sequence participant LB Controller kube-system AWS API · ELBv2 · Sequence participant AWS API ELBv2 ALB / NLB · provisioned resource · Sequence participant ALB / NLB provisioned resource Legend request return async trace default message