Field Guides / Ingress NGINX to Gateway API
Field Guide · Intermediate to Advanced · 10-12 hours with labsIngress NGINX Is Retired: Migrate to Gateway API
Move off the retired ingress-nginx controller to Gateway API with tested mappings, labs and a zero-downtime cutover runbook.




81
pages
pages
12
hands-on labs
hands-on labs
25
interview Q&As
interview Q&As
13
chapters
chapters
This is for you if
- You run ingress-nginx in production and need a safe, supported way off it
- You own a platform and must pick a Gateway API implementation your teams can live with
- You're the one who gets paged if the migration breaks a redirect, a certificate or a canary
- You're preparing for platform, SRE or DevOps interviews where this migration comes up
What's inside
- The official retirement timeline and what it means for your risk, plus an inventory script for your clusters
- GatewayClass, Gateway, HTTPRoute, GRPCRoute, ReferenceGrant and ListenerSet explained through status conditions
- Policy attachment and a scored way to choose between Envoy Gateway, Istio, Cilium, NGINX Gateway Fabric and cloud options
- Annotation-by-annotation mapping tables, including the hidden ingress-nginx defaults that cause outages
- A review workflow for ingress2gateway output and its warnings, with and without emitters
- TLS with cert-manager on Gateways, BackendTLSPolicy, and the HTTP-01 parallel-run trap
- Canary weights, header and query matching, mirroring and gRPC routing
- A six-phase zero-downtime runbook with parity testing, weighted DNS and rollback at every step
- Troubleshooting table, production checklists, 25 interview Q&As, cheat sheet and a 30-day plan
After this guide you can
- Inventory any ingress-nginx footprint and turn it into a prioritized migration backlog
- Build and debug Gateway API routing by reading status conditions instead of guessing
- Translate ingress-nginx annotations, snippets and defaults into Gateway API resources and policies
- Issue and verify certificates for Gateways with cert-manager without depending on DNS cutover
- Run a parallel edge, prove parity and cut over with weighted DNS and a tested rollback
- Answer senior-level interview questions about Gateway API and ingress migrations
Contents
- The retirement, and the mental model you needp. 4
- The core resources, hands-onp. 11
- Policy attachment and choosing an implementationp. 23
- Mapping ingress-nginx annotations to Gateway APIp. 29
- The ingress2gateway toolp. 38
- TLS with cert-managerp. 42
- Canary, header matching and gRPCp. 48
- The zero-downtime migration runbookp. 54
- Troubleshooting playbookp. 60
- Production checklist and design decisionsp. 64
- Interview questionsp. 66
- Cheat sheetp. 75
- Your 30-day practice planp. 79
Written by Randy, a Senior Platform Engineer & SRE who runs production platforms on AWS, GCP and Azure. Companion to the Techworld with Randy episode Ingress NGINX to Gateway API.