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 →Securing GitHub Actions: Best Practices for Dependency Management
In a world where CI/CD pipelines are critical, securing your GitHub Actions dependencies is non-negotiable. Pinning versions and enforcing strict permissions can prevent vulnerabilities from third-party actions. Let's dive into how to implement these strategies effectively.
Unlocking Performance with Kubernetes Pod-Level Resource Managers
Kubernetes v1.36 introduces Pod-Level Resource Managers, a game changer for performance-sensitive workloads. This feature allows for hybrid resource allocation models, enhancing efficiency without compromising NUMA alignment.
Streamline Your Hybrid Kubernetes Networking with EKS Hybrid Nodes Gateway
Hybrid cloud environments are complex, but the Amazon EKS Hybrid Nodes gateway simplifies networking between on-premises and cloud resources. By leveraging Cilium's VXLAN Tunnel Endpoint feature, it creates seamless connections that keep your applications running smoothly.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.