Kubernetes is set to retire its Ingress NGINX controller in March 2026, a decision that highlights the ongoing struggles with maintaining open source projects. Ingress NGINX has been crucial for managing HTTP and HTTPS traffic within Kubernetes clusters, yet it has suffered from inadequate support. With only one or two maintainers working on it in their spare time, the project has become a liability, especially after a critical security vulnerability was discovered that could allow attackers to take over entire clusters. The maintainers announced their intention to develop a replacement controller, but that effort didn't attract enough contributors. The frustration surrounding Ingress NGINX's retirement is palpable, particularly among its users. Some feel that a longer transition period is necessary, given the project's significance. However, Kubernetes maintainer Tim Hockin pointed out that the maintainers have been working without compensation and emphasized the lack of new volunteers willing to take on the responsibility. The broader issue is not just Ingress NGINX; it reflects a troubling trend in open source software, where vital projects often rely on unpaid labor. William Morgan, CEO of Buoyant, argues that the current structure of the Cloud Native Computing Foundation (CNCF) ecosystem promotes consumption over contribution. He proposes that projects need financial backing from companies that benefit directly or indirectly from them. The problems faced by Ingress NGINX mirror those of other crucial open source projects, like FFmpeg, which also struggles with demands for maintenance without sufficient funding. The reality is that as open source software becomes more essential, the need for a sustainable model to support its development is urgent.