Services
Ingress NGINX
cutover.
SIG Network is retiring Ingress NGINX. Resizes runs the same kind of cutover it already published: from Ingress NGINX to Envoy Gateway on EKS, with the old controller left up until each host is proven.
What the published cutover included
The field note is the public account. It describes one production EKS estate, three traffic lanes, about 40 Ingress objects, about 50 hostnames on Envoy, GitOps with Argo CD, and a team of two to three platform engineers. Three days is the DNS cutover window, not the whole programme. The note records no user-visible outage, no DNS rollback, and no incidents filed in the change log for that window.
The method in that note is dual-run and canary DNS per hostname. ingress2gateway does not cover every annotation. The offer is to run that cutover with your team, on your cluster, as platform engineering services. The checklist is Ingress NGINX retirement.
Where it sits
A cutover can stand alone or land on Resizes Platform, the managed internal developer platform. It is not a Dash product. Dash is retired.