Course contentsShow
← Cloud and Infrastructure
Lesson 1220 of 2,98924. Kubernetes NetworkingFree lesson

Ingress vs Service Load Balancing

Compare Ingress with LoadBalancer Services and learn when to use each for external traffic management.

Ingress vs Service Load Balancing

You'll learn when to use Ingress versus LoadBalancer Services for routing external traffic to your Kubernetes applications.

Both Ingress and LoadBalancer Services get external traffic into your cluster, but they work at different layers and solve different problems.

LoadBalancer Services

A LoadBalancer Service provisions a cloud load balancer (like AWS ELB or GCP Load Balancer) for each Service. It operates at Layer 4 (TCP/UDP), meaning it routes traffic based on IP addresses and ports. When you create a LoadBalancer Service, your cloud provider gives you one external IP address that forwards traffic directly to your Pods.

The catch? Each LoadBalancer Service gets its own cloud load balancer—and that costs money. If you have ten services, you're paying for ten separate load balancers.

Ingress Resources

An Ingress operates at Layer 7 (HTTP/HTTPS), allowing you to route traffic based on URLs, hostnames, and paths. Think of it as an intelligent traffic cop: one Ingress can handle multiple services using path-based or host-based routing. For example, example.com/api → Service A, example.com/web → Service B.

Key advantage: You need only one load balancer (managed by an Ingress Controller) to handle traffic for many services—saving cost and complexity.

When to Use Each

  • Use LoadBalancer when you need simple TCP/UDP routing, non-HTTP protocols, or have just one service to expose.
  • Use Ingress when serving HTTP/HTTPS traffic for multiple services, need path/host routing, SSL termination, or want cost efficiency at scale.

Key Takeaway: LoadBalancer Services create one cloud load balancer per service at Layer 4, while Ingress consolidates multiple services behind a single load balancer with Layer 7 routing rules—making Ingress more cost-effective for HTTP applications.