<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GCP on jakubszostak</title>
    <link>https://jakubszostak.pl/tags/gcp/</link>
    <description>Recent content in GCP on jakubszostak</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 13 Jan 2026 22:10:00 +0100</lastBuildDate>
    <atom:link href="https://jakubszostak.pl/tags/gcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Scaling ArgoCD to 3000&#43; Applications: HA and Multi-Cluster Sharding</title>
      <link>https://jakubszostak.pl/posts/scaling-argocd-ha/</link>
      <pubDate>Tue, 13 Jan 2026 22:10:00 +0100</pubDate>
      <guid>https://jakubszostak.pl/posts/scaling-argocd-ha/</guid>
      <description>&lt;p&gt;As organizations grow, so does their GitOps footprint. Managing a couple dozen applications with ArgoCD is a walk in the park — you install it, point it at your repo, and everything &lt;em&gt;just works&lt;/em&gt;. It&amp;rsquo;s beautiful. You start bragging about GitOps on Reddit. Life is good.&lt;/p&gt;&#xA;&lt;p&gt;Then you hit &lt;strong&gt;3,000+ applications&lt;/strong&gt; across dozens of Kubernetes clusters.&lt;/p&gt;&#xA;&lt;p&gt;Suddenly, reconciliation loops take forever. The UI feels like it&amp;rsquo;s running on a potato. The &lt;code&gt;application-controller&lt;/code&gt; starts getting OOM-killed at 3 AM, and your on-call engineer is questioning their career choices. Your Slack channel fills up with &amp;ldquo;is ArgoCD down again?&amp;rdquo; messages, and you start wondering if maybe spreadsheets were fine all along.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
