World map

 

BM

World K3: Counters & Doors

Ingress, and why ingress-nginx retired

You will learn: what Ingress is, why ingress-nginx retired, and what to do now.

Checked with Kubernetes 1.37 on 31 Oct 2026

The problem

Your new team’s cluster is full of Ingress files. You read that ingress-nginx retired. Is the cluster broken now?

Watch

Tap each point on the timeline.

Ingress: The older way in: one object for the door and its paths. Gateway API replaces it. is the older way in. One object holds the door and its paths. A separate controller, like ingress-nginx, does the work.

Watch

Same job, two styles. Sort each feature.

Drag a card into a box. Or tap the card, then tap the box.

      Try it

      This Ingress comes from an old blog post. It won’t apply on Kubernetes 1.37. Fix the first line.

      Fix the manifest, then press Apply.

      ingress.yaml16 lines

      Plain words: Kubernetes no longer knows Ingress under that old group.

      Check

      Why did ingress-nginx retire?

      Check

      Your cluster still runs ingress-nginx. Judge each plan.

      Swipe right for good, left for needs work. Or use the buttons.

      1 / 5

      Plan a move to Gateway API.

      You did it!

      You can now read an Ingress, and explain the move to Gateway API.

      Go deeper (optional)

      Careful with names: F5’s NGINX Ingress Controller is a separate project. If you must keep Ingress, pick another maintained controller from the Kubernetes docs. Ingress still shows up on exams and older clusters, so it’s worth reading.

      Real rep (optional), on a cluster you may inspect (admin rights):

      Real mission

      1. kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx
      2. kubectl get ingressclass

      0 of 2 steps done · Your ticks are saved.