<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gateway-Api on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/gateway-api/</link><description>Recent content in Gateway-Api on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 04 Aug 2026 12:54:10 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/gateway-api/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Gateway API v1.6: TCPRoute and UDPRoute reach GA</title><link>https://curadevops.metacog.co.kr/insights/2026-08-04-gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard/</link><pubDate>Tue, 04 Aug 2026 12:54:10 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-04-gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> TCPRoute and UDPRoute are now stable in the v1 API, making portable L4 routing viable for production workloads like databases, DNS, and VoIP. If you&amp;rsquo;re already using experimental Gateway API resources, audit for the new gateway.networking.x-k8s.io API group separation to avoid breakage on upgrade.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Gateway API continues maturing as the unified Kubernetes networking standard; L4 GA coverage strengthens the case for standardizing on it as the org&amp;rsquo;s golden-path ingress model over implementation-specific CRDs.&lt;/li>
&lt;/ul></description></item></channel></rss>