Replacing Ingress NGINX
Ingress NGINX has been a key component in many Kubernetes environments for years. But with the shift towards the Kubernetes Gateway API, platform, DevOps and security teams need to reassess their ingress architecture: configurations, operational processes, monitoring, runbooks and responsibilities must be reviewed or adapted.
Turn the replacement into a security upgrade
Now is the right time not only to replace the existing ingress controller, but also to assess whether the current setup still meets the requirements of modern Kubernetes environments.
Today, platform teams need more than routing and TLS termination. They need a solution that supports the Gateway API, represents security declaratively, protects APIs, takes identities into account and integrates cleanly into DevSecOps and GitOps processes.
This is where Airlock Microgateway comes in: a Kubernetes-native solution for the Gateway API, Web Application and API Protection (WAAP) and identity-based access control.
Why Airlock Microgateway is the better option
| Ingress NGINX | Airlock Microgateway with Gateway API |
| Officially retired on 24 March 2026 | Ready for what comes next Built on Envoy and open standards: Gateway API, OIDC and Red Hat certification. |
| Ingress API is frozen – architectural dead end | Gateway API Kubernetes-native without annotations. Role-oriented configuration (Gateway API) and separation of concerns. |
| Critical 'Ingress Nightmare' CVEs | Secure by Default Allowlisting with OpenAPI or GraphQL validation. ICAP for malware and Bug Bounty tested deny rules. |
| Limited Authentication use cases | Built-in identity & access control Client certificate authentication, OIDC, token introspection, JWT/JWKS, Token Exchange, step-up authentication (MFA). |
Make Gateway API part of your security strategy
With Airlock Microgateway, you bring key security capabilities closer to your Kubernetes workloads and integrate them into modern DevSecOps processes.
For your team, this means:
- A modern Gateway API architecture instead of legacy Ingress
- Protection for web applications and APIs directly in Kubernetes
- Identity-based access control with OIDC, JWT and Token Exchange
- Declarative configuration for GitOps and DevSecOps workflows
- Professional support for production Kubernetes environments
The documentation shows how migration to the Gateway API works with Airlock Microgateway.
Plan your migration to the Gateway API
Use the replacement as an opportunity to discover Airlock Microgateway with Gateway API, WAAP and identity-based access control in one solution.
If you would like to find out more, need assistance or would like to book a demo, please contact us. Our experts will get back to you shortly.
The era of the Gateway API is here
The Gateway API is replacing Ingress as the standard for modern Kubernetes architectures. But the change is more than just a technical migration: modern Ingress architectures require not only flexible routing, but also integrated security. Anyone migrating away from Ingress NGINX now should therefore fundamentally rethink their architecture – using the Gateway API, WAAP and identity-based access control directly within Kubernetes.