Course contentsShow
← Cloud and Infrastructure
Lesson 1583 of 2,98932. Service Mesh FoundationsFree lesson

Gateway Resource for Ingress

Learn how Gateway configures load balancers for external traffic entering the mesh.

Gateway Resource for Ingress

What You'll Learn

You'll learn how Istio's Gateway resource configures external load balancers to route traffic entering your service mesh.

The Front Door to Your Mesh

While VirtualService handles routing within your mesh and DestinationRule defines traffic policies for specific services, the Gateway resource is your mesh's front door—it configures how external traffic enters your service mesh in the first place.

Think of a Gateway like a hotel's main entrance. The building has many internal corridors (VirtualServices) and room-specific rules (DestinationRules), but first you need a controlled entrance where security checks happen and visitors are directed to the right lobby area.

How Gateway Works

A Gateway configures a load balancer (typically Envoy proxies running on dedicated ingress pods) to:

  • Listen on specific ports (80 for HTTP, 443 for HTTPS)
  • Accept traffic for certain hostnames (like myapp.example.com)
  • Terminate TLS/SSL if configured
  • Pass traffic to VirtualServices that bind to the Gateway

The Gateway itself doesn't do routing to backend services—it just opens the door. You then bind VirtualServices to your Gateway to handle the actual routing logic. This separation keeps concerns distinct: Gateways manage external connectivity, VirtualServices manage routing.

Gateway and Load Balancer Relationship

When you create a Gateway resource, Istio configures the underlying Envoy proxies that function as load balancers at the mesh edge. These proxies listen for the ports and protocols you specify, handle TLS termination if configured, and forward acceptable traffic into the mesh where your VirtualServices take over.

Key Takeaway: Gateway resources configure edge load balancers to accept external traffic into your service mesh on specific ports and hosts, acting as the controlled entry point before VirtualServices handle internal routing.