Translate the following blog post title into English, concise and natural. Return plain text only without quotes. Kubernetes 社区宣布停止支持 Ingress NGINX 控制器
Kubernetes Announces Retirement of Ingress NGINX
The Kubernetes SIG Network and the Security Response Committee have announced the retirement of Ingress NGINX, one of the most widely used ingress controllers in the Kubernetes ecosystem.
Best-effort maintenance will continue until March 2026, after which there will be no further releases, bug fixes, or security updates. This was confirmed during KubeCon NA 2025.
---
Background: Why It Matters
- Ingress NGINX has served for years as a foundational component for routing traffic to workloads.
- Its rich feature set, flexibility, and cloud-provider independence drove early adoption.
- Maintainership challenges: Only one or two individuals have been contributing in their spare time, with failed attempts to expand the maintainer base.
- The maintainers acknowledge the controller has handled billions of requests globally, from enterprise data centers to home labs.
---
Technical Debt & Security Concerns
The maintainers cite unsustainable technical debt as a key reason for retirement.
- Flexible features like "snippets" annotations enabled arbitrary NGINX config directives.
- Initially a strength, these now represent serious security risks in modern cloud-native deployments.
---
Abandoned Replacement Effort
A planned successor called InGate never gained traction and will also be retired alongside Ingress NGINX.
---
Community Guidance: Migrate to Gateway API
Why Gateway API?
- Designed to overcome limitations of original Ingress specification.
- Provides a role-based architecture separating responsibilities between:
- Infrastructure providers
- Cluster operators
- Application developers
- Reached General Availability in late 2023.
Benefits Over Ingress NGINX
- Native support for TCP, UDP, gRPC in addition to HTTP/HTTPS.
- Advanced features: traffic splitting, header-based routing, all without annotations.
- Eliminates vendor-specific workarounds previously needed.
---
Alternatives to Gateway API
For teams unable to adopt Gateway API immediately, options include:
- NGINX commercial offerings
- Kong
- Traefik
- HAProxy (migration tool here)
---
Migration Impact
Cloud-native advocate Jimmy Song calls this “a pivotal moment in infrastructure evolution”:
> Once infrastructure components can no longer be securely updated, they cease to be assets and become liabilities.
Key points from Song:
- Problem isn’t usage decline — it’s maintenance sustainability.
- Most users treated Ingress NGINX as a black box.
- Retirement may cause a hidden migration wave across clusters.
- Expect effort to shift toward unified, extensible APIs in infrastructure projects.
---
Checking If You Use Ingress NGINX
Run this command (requires cluster admin permissions):
kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginxThis lists all pods matching the Ingress NGINX label across namespaces, helping determine usage.
---
Action Plan
- Verify usage in your clusters.
- Plan migration early to remain reliable, secure, and compliant.
- Evaluate Gateway API or alternative controllers.
---
Related Developments: AI & Content Workflow Platforms
While infrastructure migration is technical, the principles of automation, orchestration, and sustainability apply more broadly.
Platforms like AiToEarn enable:
- AI-driven content generation
- Cross-platform publishing (Douyin, Kwai, WeChat, Bilibili, Facebook, Instagram, LinkedIn, Threads, YouTube, Pinterest, X)
- Analytics and model ranking
These integrated workflows mirror the kind of streamlining and modernization Gateway API brings to network traffic management.
Learn more:
---
Bottom line: Migrating away from Ingress NGINX is inevitable. Proactive planning — combined with adopting modern, extensible tools — will minimize risk and ensure your infrastructure remains secure and future-ready.
