AWS Advanced Networking Speciality 1.3: AWS Load Balancer Controller for Kubernetes clusters

List of blogs on AWS Advanced Networking Speciality Exam — https://medium.com/@raaki-88/list/aws-advanced-network-speciality-24009c3d8474

Various Aspects of this post

Before understanding LoadBalancer Service, it’s worth understanding a few things about NodePort service.

NodePort Service :

NodePort service opens a port on each node. External agents can connect directly to the node on the NodePort. If not mentioned, a randomly chosen service is picked up for NodePort. LoadBalancing here is managed by front-end service, which listens to a port and load balances across the Pods, which responds to service requests.

Node Port Service — Ref: https://static.us-east-1.prod.workshops.aws/public/cc03eca7-e91d-428b-a4a2-78e2b81b5114/static/images/service_nodeport_1.png

LoadBalancer Service:

Sample NLB / LB Service — https://static.us-east-1.prod.workshops.aws/public/cc03eca7-e91d-428b-a4a2-78e2b81b5114/static/images/service_load_balancer_6.png

Like NodePort Service, the LoadBalancer service extends the functionality by adding a load balancer in front of all the nodes. Kubernetes requests ELB and registers all the nodes. It’s worth noting that Load Balancer will not detect where the pods are…