<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ingress on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/ingress/</link><description>Recent content in Ingress on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Jul 2026 12:56:53 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/ingress/index.xml" rel="self" type="application/rss+xml"/><item><title>AKS Application Routing with Gateway API reaches GA</title><link>https://curadevops.metacog.co.kr/insights/2026-07-29-launched-generally-available-application-routing-with-gatewa/</link><pubDate>Wed, 29 Jul 2026 12:56:53 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-29-launched-generally-available-application-routing-with-gatewa/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> The Kubernetes Gateway API is the intended successor to the Ingress API, and it&amp;rsquo;s now GA on AKS — plan a migration evaluation from existing Ingress controllers to the managed Gateway API offering this quarter. No forced deadline exists, but adopting early reduces future migration debt as the Ingress API ages out.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Gateway API going GA on AKS signals accelerating industry standardization on the new Kubernetes networking model, worth tracking as context for ingress-tooling decisions if an AKS golden-path review is upcoming.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item><item><title>Kubernetes ingress-nginx announces retirement</title><link>https://curadevops.metacog.co.kr/insights/2026-07-15-kubernetes-ingress-nginx-is-retiring/</link><pubDate>Wed, 15 Jul 2026 12:10:55 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-15-kubernetes-ingress-nginx-is-retiring/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> ingress-nginx is one of the most widely deployed Kubernetes ingress controllers; its retirement means planning a migration to an alternative (e.g., Envoy Gateway, NGINX Gateway Fabric, or another Gateway API-conformant controller). No forced migration date is confirmed yet, so scope the migration project now before community support winds down.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If ingress-nginx is part of the org&amp;rsquo;s Kubernetes golden path or standard stack, its retirement requires evaluating replacement ingress controllers and updating platform standards; begin that toolchain review this planning cycle before the project loses maintainer support.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item></channel></rss>