<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ingress-Nginx on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/ingress-nginx/</link><description>Recent content in Ingress-Nginx on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 11:00:57 -0500</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/ingress-nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>ingress-NGINX retirement: migrate off the retired SIG Network controller</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-navigating-the-ingress-nginx-retirement/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-navigating-the-ingress-nginx-retirement/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Act:&lt;/strong> ingress-nginx reached end-of-life in March 2026 (now four months past); remaining on it means exposure to unpatched CVEs in a critical ingress path with no upstream fixes coming. Audit clusters for ingress-nginx usage and complete migration to a maintained alternative (Envoy Gateway, Ingress-NGINX from F5, Traefik) immediately.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> The SIG Network ingress-nginx controller is retired, making any org standardized on it subject to growing unpatched CVE exposure with no remediation path; this warrants a brief to leadership and a decision on a replacement ingress standard before the vulnerability surface widens further.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item></channel></rss>