Ingress NGINX: The Urgent Migration You Can't Ignore
Ingress NGINX serves as a backbone for around half of cloud-native environments, managing traffic routing and access control. However, with its impending retirement in March 2026, it's crucial to assess your reliance on this tool. If you continue using Ingress NGINX post-retirement, you expose yourself and your users to significant security risks.
To determine if your clusters depend on Ingress NGINX, run the command: kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx. This command requires cluster administrator permissions and will help you identify any active deployments. Existing setups will keep functioning unless you actively check, which means you might remain unaware of vulnerabilities until it's too late.
It's imperative to start planning your migration away from Ingress NGINX now. The longer you wait, the greater the risk to your infrastructure. The transition to alternatives like the Gateway API should be prioritized to maintain security and functionality in your Kubernetes environment.
Key takeaways
- →Run `kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx` to check your cluster's reliance on Ingress NGINX.
- →Plan your migration to alternatives like the Gateway API before Ingress NGINX is retired in March 2026.
- →Understand that continuing to use Ingress NGINX post-retirement leaves your deployments vulnerable.
- →Recognize that existing deployments will not alert you to vulnerabilities unless you proactively check.
- →Act now to secure your infrastructure and avoid potential compromises.
Why it matters
Failing to migrate from Ingress NGINX before its retirement can lead to significant security vulnerabilities, jeopardizing your entire cloud-native infrastructure.
Code examples
kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginxWhen NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsUnified observability — logs, uptime monitoring, and on-call in one place. Used by 50,000+ engineering teams to ship faster and sleep better.
Try Better Stack free →Injecting Chaos: My LFX Mentorship with kgateway
Chaos engineering is essential for resilient systems, and kgateway makes it easier to implement. I focused on adding HTTP fault injection support, enabling teams to test their services against real-world failures. This article dives into how I achieved this and what you need to know to leverage it effectively.
Seamlessly Access Private Git Repositories in EKS with Argo CD
Unlock the power of Argo CD by integrating it with private Git repositories hosted on AWS. Learn how to set up AWS CodeConnections to create a secure network path for your Git server, ensuring smooth deployment workflows.
Mastering Full Request and Response Logging on Amazon EKS
In a world where compliance is non-negotiable, capturing full request and response data is crucial. Learn how Envoy’s External Processing filter enables this without altering your application code.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.