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 docsIndustry-standard certifications built by the people behind Linux and Kubernetes. Earn the CKA — the gold standard Kubernetes administrator cert. OpsCanary readers get 30% off year-round with code OPSCANARY3.
Get CKA certified →CiliumCon Returns: Scaling eBPF Networking at KubeCon 2026
CiliumCon is back, and it's crucial for anyone involved in Kubernetes networking. With Cilium as the de facto CNI, understanding its eBPF foundation is key to managing workloads at scale. Don't miss out on the insights that could elevate your cloud-native architecture.
OVHcloud Joins CNCF: What This Means for Kubernetes in Europe
The CNCF's new partnership with OVHcloud marks a significant shift for Kubernetes in Europe. With OVHcloud operating thousands of production Kubernetes clusters using Cilium, this collaboration promises enhanced networking and security for multi-tenant environments.
Migrating to ALB: Mastering oauth2-proxy in Kubernetes
Switching from NGINX Ingress to ALB can be tricky, especially when handling oauth2-proxy. Learn how to configure oauth2-proxy to work seamlessly with ALB's OIDC authentication capabilities.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.