"A lot of organizations aren't going to shift away from it -- even though it's got known vulnerabilities that are being exploited -- for the same reason they didn't shut it off two or three years ago, which is that it worked two or three years ago, and it still works now. Replacing it with another technology means all your APIs need to communicate correctly. The CRDs there need to be reliable.

"[Some users] could be told today that something is incredibly insecure, it's likely to be compromised, and ignore that, and say, 'But it still works at the end of the day.' That's a serious problem." ~ Nigel Douglas, head of developer relations at #CNCF member company Cloudsmith and a former contributor to the Falco CNCF project, in an interview this week about the retirement of the #IngressNginx project and its potential impact on users who might remain unaware that the project is no longer receiving community support, including security patches, following its final release March 13.

My writeup on the discussions during #KubeConEU this week: https://www.techtarget.com/searchitoperations/news/366640683/CNCF-Ingress-Nginx-retirement-could-leave-some-users-at-risk