With Ingress-NGINX entering retirement in March 2026 organizations face a critical migration deadline that demands immediate attention from platform teams. This week SIG Network delivered exactly what was needed: Ingress2Gateway 1.0, a tested migration assistant for moving from Ingress to Gateway API safely. This milestone represents a stable tested migration assistant for teams ready to modernize their networking stack for production environments. For most organizations running production Kubernetes clusters the question is not whether to migrate to Gateway API but how to do so safely and efficiently without disrupting existing workloads and applications. Ingress-NGINX has been the de facto Kubernetes ingress controller for years but its retirement means teams must migrate to the Gateway API specification immediately. This is not a simple find-and-replace operation requiring careful planning and execution. Gateway API is fundamentally different from the original Ingress specification in design philosophy. It is modular extensible and backed by native RBAC support unlike the original specification which relied heavily on annotations for functionality and behavior. The challenge Ingress2Gateway solves is significant and complex. Real-world Ingress configurations contain dozens of controller-specific annotations custom snippets and subtle behaviors accumulated over years of production operation. The challenge involves capturing those nuances and mapping them to Gateway API behavior which requires deep knowledge of both systems and their differences. Missing a CORS configuration or regex pattern can cause production outages for end users. Version 1.0 delivers three major improvements over previous releases. First it supports 30 plus Ingress-NGINX annotations up from just three in earlier releases. Version 1.0 adds comprehensive coverage for CORS backend TLS regex matching path rewrites and many more configurations that production clusters rely on for correct behavior. Second it includes real integration testing with comprehensive coverage. Each supported annotation is backed by controller-level tests against live clusters spinning up actual controllers. The test suite spins up Ingress-NGINX and multiple Gateway API controllers in real Kubernetes environments. Third it includes better error handling and reporting. Untranslatable configuration surfaces with clear warnings and suggestions so teams know exactly what needs manual review before production deployment. Using Ingress2Gateway is straightforward for platform teams. Install via Go or Homebrew with standard package managers following standard installation procedures. Generate Gateway API manifests from existing Ingress resources using the print command with provider specifications. Review warnings carefully before applying to production environments to avoid misconfigurations. The tool is an assistant not a one-click migration requiring human judgment. Teams should translate supported configuration identify unsupported config and plan alternatives with stakeholders. Testing in staging environments is essential before production rollout. Looking ahead organizations running production Kubernetes clusters need to prioritize this migration immediately. With March 2026 as the end of Ingress-NGINX support running this migration assistant should be this weeks top priority. Gateway API represents significant improvements including better RBAC cross-namespace routing and extensible backends missing from original Ingress. The migration is an opportunity to clean up years of accumulated technical debt and legacy configurations while modernizing networking infrastructure. Sources Kubernetes Blog announcing Ingress2Gateway 1.0 release. Ingress2Gateway GitHub Repository documentation.
Ingress2Gateway 1.0: Migrating from Ingress-NGINX
Next signal