Skip to content

Advertisement

DevOps Society
KubernetesAnalysis

EKS Auto Mode Now Speaks Gateway API and That Changes the Ingress Migration Math

EKS Auto Mode now handles Gateway and HTTPRoute resources with no controller to install. With ingress-nginx retired, here is how to plan the move from Ingress on EKS.

Published your local timeupdated

EKS Auto Mode Now Speaks Gateway API and That Changes the Ingress Migration Math

For most Kubernetes teams, getting traffic into a cluster has meant an Ingress resource and a controller someone installed years ago. That setup is running out of road. The community ingress-nginx controller was retired in March, and the Gateway API is now where the upstream work happens. AWS just made the move easier for one group of users.

What did AWS add to EKS Auto Mode?

On 28 October, AWS said EKS Auto Mode now supports the Kubernetes Gateway API. You describe load balancing with Gateway and HTTPRoute resources and Auto Mode builds and manages the AWS side. There is no separate controller to install or upgrade.

The feature list covers what most teams use day to day:

  • HTTP and gRPC routing.

  • Cross-namespace routing, so a platform team can own the Gateway while app teams own their routes.

  • Weighted traffic splitting for canary releases.

  • Header-based routing.

  • Automatic TLS certificate discovery from AWS Certificate Manager.

Existing Ingress resources keep working next to the new ones. The feature is included with Auto Mode, and you pay the normal load balancer charges. Setup details are in the EKS user guide.

Why does Gateway API matter?

Ingress was one resource doing two jobs. The person who owns the load balancer and the person who owns an app's routes edited the same object, and anything beyond basic routing lived in controller-specific annotations. That is why moving between controllers is painful: the real configuration is in strings like nginx.ingress.kubernetes.io/*.

Gateway API splits the roles. A Gateway is infrastructure, owned by the platform team. HTTPRoutes belong to app teams and attach to a Gateway they are allowed to use. Traffic splitting and header matching are part of the spec instead of annotations, so they move between implementations.

Where does ingress-nginx fit in?

Kubernetes SIG Network retired the community ingress-nginx controller in March 2026. The Ingress API itself is not going away, but the controller no longer gets fixes, so any new CVE stays open. CNCF's guidance lays out two paths: swap to another Ingress controller as a stopgap, or move to Gateway API.

For EKS Auto Mode users, the second path now has no extra moving parts.

How should you plan the move?

  1. Audit your annotations. List every controller annotation in use across clusters. Those are your real migration work.

  2. Translate with tooling, then review by hand. The ingress2gateway project converts many Ingress resources to Gateway API. Treat its output as a draft.

  3. Run both side by side. Because Ingress keeps working, stand up a Gateway and routes for a non-critical service, shift DNS or traffic gradually and watch error rates.

  4. Decide who owns the Gateway. The biggest win is organisational. Give the platform team the Gateway and app teams their routes, and write down which namespaces may attach.

  5. Check what Auto Mode does not cover. If you rely on advanced features from your current controller, such as custom rate limiting or auth plugins, confirm the managed implementation supports them before you commit.

Teams not on Auto Mode still have good options, including the AWS Load Balancer Controller, which added Gateway API support earlier this year. The direction is the same everywhere: new routing work should start on Gateway API.

Quick answers

Does EKS Auto Mode support the Gateway API?

Yes. Since 28 October 2026, EKS Auto Mode supports Gateway and HTTPRoute resources with HTTP and gRPC routing, cross-namespace routing, weighted splitting, header-based routing and ACM certificate discovery, without a separate controller.

Is the Kubernetes Ingress API deprecated?

No. The Ingress API still works but is feature-frozen. The community ingress-nginx controller was retired in March 2026, and Gateway API is the actively developed successor.

Can Ingress and Gateway API run together on EKS?

Yes. On EKS Auto Mode, existing Ingress resources keep working alongside Gateway API resources, which allows a gradual migration.

Advertisement

Follow DevOps Society on LinkedIn

Practical infrastructure engineering in your feed.

Follow

Written by

DevOpsSociety Editorial Team

Editorial Team

The DevOpsSociety Editorial Team covers DevOps, cloud infrastructure, Kubernetes, AI infrastructure, platform engineering, cybersecurity, FinOps, and modern engineering practices. We publish practical insights, technical guides, architecture analysis, and research for engineers and technology leaders.

More from DevOpsSociety →
The Infrastructure Briefing

Get the infrastructure briefing.

Practical DevOps, cloud, AI infrastructure and engineering insights, delivered weekly. Read by engineers and engineering leaders.

No spam. Unsubscribe anytime.

EKS Auto Mode Now Speaks Gateway API and That Changes the Ingress Migration Math, DevOps Society