---
title: "Ingress NGINX cutover | Resizes"
url: "https://resiz.es/services/ingress-nginx-cutover"
description: "Resizes runs Ingress NGINX cutovers to Gateway API. The public field note covers an EKS move to Envoy Gateway: dual-run, canary DNS, and a three-day cutover."
---

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](https://resiz.es/blog/ingress-to-gateway-migration) 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](https://resiz.es/services/platform-engineering). The checklist is [Ingress NGINX retirement](https://resiz.es/guides/ingress-nginx-retirement).

## Where it sits

A cutover can stand alone or land on [Resizes Platform](https://resiz.es/products/platform), the [managed internal developer platform](https://resiz.es/services/managed-internal-developer-platform). It is not a Dash product. Dash is [retired](https://resiz.es/dash).

[Talk about a cutover →](https://resiz.es/contact)