Services LoadBalancer

In this lesson, we’ll explore the Kubernetes Service type LoadBalancer. We begin with a quick recap of NodePort, then introduce LoadBalancer and demonstrate how to provision a cloud load balancer automatically.

1. Recap: Kubernetes NodePort Service

A NodePort exposes a Service on a static port (the NodePort) on every node in your cluster. For example, if you expose the voting app on port 31000 and the result app on port 32000, external users can reach them via:

• http://<node-ip>:31000
• http://<node-ip>:32000

Even if your Pods run only on nodes with IPs 10.0.0.70 and 10.0.0.71, they remain accessible on the same port across all nodes in the cluster.

2. Limitations of NodePort

While NodePort is straightforward, it has some drawbacks:

• No single friendly URL for end users
• Manual management of external load balancer infrastructure
• Exposure of high-range ports (30000–32767)

3. Introducing the LoadBalancer Service

On supported cloud platforms (GCP, AWS, Azure), setting type: LoadBalancer in your Service manifest will:

1. Provision a native cloud load balancer
2. Configure forwarding rules to cluster nodes
3. Distribute traffic across Service endpoints

Here’s a sample voting-service.yaml:

apiVersion: v1
kind: Service
metadata:
  name: voting-app
spec:
  type: LoadBalancer
  selector:
    app: voting
  ports:
    - port: 80
      targetPort: 80

Apply it with:

kubectl apply -f voting-service.yaml
kubectl get svc voting-app
# NAME         TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)        AGE
# voting-app   LoadBalancer   10.0.173.200   34.68.123.456   80:32000/TCP   1m

4. Comparing Service Types

Links and References

• Kubernetes Services
• LoadBalancer Service
• Cloud Provider Integration