Kubernetes

Ingress & Gateways

Route external HTTP traffic into the cluster.

35 min read intermediate 3 objectives

Status

Not started

What you will learn

  • Configure Ingress rules
  • Terminate TLS
  • Understand the Gateway API

New to this? Start here

The basics, in plain English

A Service can expose an app, but managing one public entry per app gets messy. Ingress is a single smart front door that routes incoming web traffic to the right Service based on the URL.

Ingress
A rulebook that routes outside web traffic to the correct Service by hostname or path.
Ingress controller
The actual program (often nginx) that reads those rules and does the routing.
Route
A rule like “send shop.example.com to the shop Service”.
TLS termination
Handling HTTPS encryption at the front door so apps behind it stay simple.
Gateway API
A newer, more flexible standard that is gradually replacing Ingress.
01

The front door

An Ingress controller routes external HTTP by host and path to Services. The newer Gateway API generalizes this with richer routing.

Finished this topic?

Mark it done to earn 100 XP and keep your streak alive.