<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on API Course</title>
    <link>https://apicourse.com/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Istio 1.31 Adds Agentgateway as a Waypoint, Giving AI Agent API Traffic Its Own Proxy</title>
      <link>https://apicourse.com/istio-1.31-adds-agentgateway-as-a-waypoint-giving-ai-agent-api-traffic-its-own-proxy/</link>
      <pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/istio-1.31-adds-agentgateway-as-a-waypoint-giving-ai-agent-api-traffic-its-own-proxy/</guid>
      <description>&lt;p&gt;Istio 1.31 is out, and one line in the release notes says a lot about where API infrastructure is heading. You can now run agentgateway, a proxy built for AI agent and MCP traffic, as a waypoint inside the mesh.&lt;/p&gt;&#xA;&lt;p&gt;If &amp;ldquo;waypoint&amp;rdquo; means nothing to you yet, that&amp;rsquo;s fine. Here&amp;rsquo;s the short version, then why it matters if you build APIs.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-changed-in-131&#34;&gt;What changed in 1.31&lt;/h2&gt;&#xA;&lt;p&gt;Istio&amp;rsquo;s ambient mode splits the mesh in two. A small per-node component handles encryption and basic connectivity. Anything that needs to understand HTTP, like routing, auth policy or rate limits, goes through a separate proxy called a waypoint. You opt services into a waypoint with a label.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
