Typorithm · medium

Ingress

ingresskubernetesroutingl7

Saved on this device

Full lesson · 8 learning steps Open any exercise for focused practice

Step 1 of 8 · intro card

Learn Ingress

Networking

An Ingress does L7 host- and path-based HTTP routing, sending requests for a given host/path to the right backend Service through a single entry point.

An Ingress is a layer-7 router: it inspects the HTTP Host header and URL path to decide where a request goes.

Rules match by host (domain) and by path, then forward to a named backend Service and its port.

An Ingress controller (NGINX, Traefik, a cloud LB) actually implements the rules, so one external IP can serve many hosts and paths.

Ingress routes HTTP by host and path (L7).

Each rule's backend points at a Service + port.

An Ingress controller must run to enforce rules.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web
spec:
  rules:
    - host: shop.example.com
      http:
        paths:
          - path: /api
            pathType: Prefix
            backend:
              service:
                name: api
                port:
                  number: 80

Read the implementation

Connect each part of the code to the concept before you type.

1. Ingress object

An Ingress defines L7 (HTTP) routing rules in front of cluster Services.

kind: Ingress

2. Host rule

host matches the request's Host header, routing by domain name.

host: shop.example.com

3. Path match

path matches the URL path; combined with pathType it selects the backend.

path: /api

4. Backend Service

backend.service.name points the matched traffic at a ClusterIP Service.

service:
                name: api

A complete learning loop

Understand

Read the concept map and follow the code breakdown.

Reconstruct

Type the implementation, repair mistakes and work through every recall exercise.

Verify

Use the final check without hints; revisit weak concepts in short practice sessions.