Ingress NGINX To Be Retired
The Kubernetes SIG Network and the Security Response Committee has announced the upcoming retirement of the Ingress NGINX Kubernetes controller.
“Best-effort maintenance will continue until March 2026. Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered,” says Tabitha Sable in the announcement. The decision was made in order “to prioritize the safety and security of the ecosystem.”
Sable notes that “existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available.” Additionally, the GitHub repositories will remain available in read-only format.
The committee recommends migrating to Gateway API immediately. Other Ingress controller options can be found in the Kubernetes documentation.
Learn more at Kubernetes.
Related content
-
Correctly integrating containers
If you run microservices in containers, they are forced to communicate with each other – and with the outside world. We explain how to network pods and nodes in Kubernetes. -
Serverless applications with OpenFaaS
Use advanced techniques for automation, optimization, and security to deploy serverless applications with the OpenFaaS framework in a Linux environment. -
Run Kubernetes in a container with Kind
Create a full-blown Kubernetes cluster in a Docker container with just one command. -
Azure Application Gateway load distribution tool
In the Azure cloud, Microsoft offers the Azure Application Gateway managed service as a Layer 7 load balancer that needs virtually no internal resources to set up and operate. -
Safeguard and scale containers
Security, deployment, and updates for thousands of nodes prove challenging in practice, but with CoreOS and Kubernetes, you can orchestrate container-based web applications in large landscapes.