<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Worker-Pools on RLGeeX</title><link>https://www.rlgeex.com/tags/worker-pools/</link><description>Recent content in Worker-Pools on RLGeeX</description><generator>Hugo</generator><language>en-us</language><copyright>RLGeeX © 2025 - Real-Life Geeks providing expert IT consulting</copyright><lastBuildDate>Tue, 03 Nov 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://www.rlgeex.com/tags/worker-pools/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloud Run as an Agent Runtime: Resource Type, Sandboxes and Agent Identity</title><link>https://www.rlgeex.com/news/cloud-run-as-an-agent-runtime-resource-type-sandboxes-and-agent-identity/</link><pubDate>Tue, 03 Nov 2026 09:00:00 -0500</pubDate><guid>https://www.rlgeex.com/news/cloud-run-as-an-agent-runtime-resource-type-sandboxes-and-agent-identity/</guid><description>&lt;p>If you lead a platform or infrastructure team and are wiring agents into real systems on Google Cloud, Cloud Run&amp;rsquo;s documentation now covers a lot of the agent runtime. Here is how I&amp;rsquo;d work through it. Hosting an agent on Cloud Run is three separate decisions, made for each agent. The first is which resource type matches the agent&amp;rsquo;s loop. The second is where its untrusted tool code runs. The third is which identity it holds. Make the identity decision first, because the functional and identity types can&amp;rsquo;t be changed or unset once you set them on a resource.&lt;/p></description></item></channel></rss>