"Kubernetes is pulling the plug on Ingress NGINX. The popular Ingress controller will be discontinued in March 2026 due to maintenance issues and security risks. Users will receive best-effort support until then. Ingress NGINX has become one of the most widely used Ingress controllers in Kubernetes. The controller enabled sending network traffic to workloads and was rolled out as standard across numerous hosted platforms. However, the project has become unsustainable."
"The breadth of features has created technical debt that is no longer manageable. Features that were once considered useful now pose serious security risks. The ability to add your own NGINX configuration via 'snippets' is one example. The number of active developers remained limited to one or two people who worked on the project in their spare time. Even a call for help last year to develop a successor did not yield any results. InGate, intended as a replacement, will not be coming either."
"After March 2026, there will be no more updates, bug fixes, or patches. The GitHub repositories will be made read-only but will remain available for reference. Existing installations will continue to work, and artifacts such as Helm charts and container images will remain accessible. Users can check whether they are running Ingress NGINX with the command 'kubectl get pods -all-namespaces -selector app.kubernetes.io/name=ingress-nginx'. This does require cluster administrator rights."
Ingress NGINX will be discontinued in March 2026, with best-effort support provided until that date. Maintenance burden, accumulated technical debt, and security risks have rendered the project unsustainable. User-provided NGINX configuration via 'snippets' is cited as one risky feature. Active development was limited to one or two part-time maintainers, and efforts to recruit successors failed; InGate will not replace it. After March 2026 repositories will be read-only while existing installations, Helm charts, and container images remain accessible. Users should migrate to Gateway API or an alternative Ingress controller; Kubernetes documentation lists options. Google introduced Agent Sandbox for Kubernetes.
Read at Techzine Global
Unable to calculate read time
Collection
[
|
...
]