<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Networking on Ajay Dhungel</title>
    <link>/tags/networking/</link>
    <description>Recent content in Networking on Ajay Dhungel</description>
    <generator>Hugo 0.125.0</generator>
    <language>en</language>
    <lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Gateway API v1.5: The End of Ingress Annotation Hell</title>
      <link>/posts/kubernetes-gateway-api/</link>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/posts/kubernetes-gateway-api/</guid>
      <description>Introduction If you have spent any meaningful time running workloads on Kubernetes, you have probably dealt with Ingress resources. They work. They get traffic into your cluster. But the moment you need something beyond basic host and path routing, you end up buried in controller-specific annotations that nobody else understands, that break the moment you switch controllers, and that give your application teams zero autonomy.&#xA;The Kubernetes Gateway API is the project&amp;rsquo;s answer to that problem.</description>
    </item>
  </channel>
</rss>
