---
title: "Ingress NGINX retirement checklist | Resizes"
url: "https://resiz.es/guides/ingress-nginx-retirement"
description: "Ingress NGINX retirement checklist from the Resizes cutover: inventory hostnames, dual-run Envoy Gateway, canary DNS, then scale NGINX down after soak."
---

Guide

# Ingress NGINX _retirement._

SIG Network is retiring Ingress NGINX. This checklist is the method in the Resizes field note: know the lanes, dual-run the replacement, move DNS per hostname, and leave NGINX up until each host is proven.

## Checklist from the published cutover

1.  List Ingress objects, IngressClasses, and hostnames. The field note covered three lanes, about 40 Ingress objects, and about 50 hostnames.
2.  Treat snippet annotations and oauth2-proxy as exceptions. ingress2gateway does not cover every annotation.
3.  Run Envoy Gateway beside NGINX. Move one hostname at a time with canary DNS.
4.  Keep GitOps as the source of the routes. The note used Argo CD and HTTPRoutes in each app.
5.  Count the DNS window separately from the programme. In the note, three days was the cutover window, and NGINX was scaled down about a week later, after soak.

The full account is the [field note](https://resiz.es/blog/ingress-to-gateway-migration). The engagement is the [Ingress NGINX cutover](https://resiz.es/services/ingress-nginx-cutover).