<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Cloud Native Architecture - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Cloud Native Architecture News feed</description>
    <item>
      <title>Netflix Adopts Cloud-Native Job Queueing System Kueue to Replace an In-House Solution</title>
      <link>https://www.infoq.com/news/2026/08/netflix-kueue-kubernetes-batch/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud+Native+Architecture-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/netflix-kueue-kubernetes-batch/en/headerimage/generatedHeaderImage-1786536066027.jpg"/&gt;&lt;p&gt;Netflix migrated most of its batch workloads onto Kueue, an open-source cloud-native batch job execution system that has outgrown its homegrown solution over the years. The company mapped the capabilities previously created in-house to Kueue’s functionality and also benefited from new features that would have been costly to incorporate into its homegrown solution.&lt;/p&gt; &lt;i&gt;By Rafał Gancarz&lt;/i&gt;</description>
      <category>Kubernetes</category>
      <category>Cloud Native Architecture</category>
      <category>Batch Processing</category>
      <category>Cell-Based Architecture</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Wed, 12 Aug 2026 14:30:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/netflix-kueue-kubernetes-batch/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud+Native+Architecture-news</guid>
      <dc:creator>Rafał Gancarz</dc:creator>
      <dc:date>2026-08-12T14:30:00Z</dc:date>
      <dc:identifier>/news/2026/08/netflix-kueue-kubernetes-batch/en</dc:identifier>
    </item>
    <item>
      <title>Pods as Workers, Not Agents: Rethinking the Deployment Unit for AI Agents on Kubernetes</title>
      <link>https://www.infoq.com/news/2026/08/pod-deployment-unit-ai-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud+Native+Architecture-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/pod-deployment-unit-ai-agents/en/headerimage/header-1785763169197.jpeg"/&gt;&lt;p&gt;Running AI agents on Kubernetes raises a key question: should each agent get its own Pod? The kagent project argues no—agents are bursty, short-lived, can spawn subagents, and may wait for human approval, making one Pod per agent wasteful. Agent-substrate adds a control plane to schedule logical “Actors” onto long-lived worker Pods.&lt;/p&gt; &lt;i&gt;By Mark Silvester&lt;/i&gt;</description>
      <category>Agents</category>
      <category>AI Architecture</category>
      <category>Kubernetes</category>
      <category>Cloud Native Architecture</category>
      <category>Cloud Native Computing Foundation</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 06 Aug 2026 06:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/pod-deployment-unit-ai-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud+Native+Architecture-news</guid>
      <dc:creator>Mark Silvester</dc:creator>
      <dc:date>2026-08-06T06:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/pod-deployment-unit-ai-agents/en</dc:identifier>
    </item>
  </channel>
</rss>
