<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ARB - GetToTheCloud</title><link>https://www.gettothe.cloud/tag/arb/</link><description>Latest ARB posts on GetToTheCloud</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 09:58:00 +0200</lastBuildDate><atom:link href="https://www.gettothe.cloud/tag/arb/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Local | Why 8 GB of RAM Isn’t Enough for Production</title><link>https://www.gettothe.cloud/azure-local-why-8-gb-of-ram-isnt-enough-for-production/</link><pubDate>Thu, 20 Aug 2026 09:58:00 +0200</pubDate><guid>https://www.gettothe.cloud/azure-local-why-8-gb-of-ram-isnt-enough-for-production/</guid><category>Azure</category><category>Azure Local</category><category>Infrastructure</category><description>Azure Local automatically deploys the Azure Resource Bridge (ARB) with 8 GB of memory, but is that really enough for production? In this article, I explore the often-overlooked control plane VM at the heart of every Azure Local deployment. Learn why larger clusters, Arc integrations, monitoring, and platform services can create memory pressure, how to spot the warning signs, and why right-sizing …</description></item></channel></rss>