<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fargate on TBNL</title>
    <link>https://www.tibobeijen.nl/tags/fargate/</link>
    <description>Recent content in Fargate on TBNL</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 18 Jul 2026 15:00:00 +0100</lastBuildDate>
    
	<atom:link href="https://www.tibobeijen.nl/tags/fargate/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Where did those 800 pods come from?</title>
      <link>https://www.tibobeijen.nl/2026/07/18/where-did-those-800-pods-come-from/</link>
      <pubDate>Sat, 18 Jul 2026 15:00:00 +0100</pubDate>
      
      <guid>https://www.tibobeijen.nl/2026/07/18/where-did-those-800-pods-come-from/</guid>
      <description>Recently I merged a pull request that was like any other pull request. But things unfolded quite differently.
Things didn&amp;rsquo;t break, but could have. Things shouldn&amp;rsquo;t have happened, but did.
The typical unlikely combination of factors, involving Argo CD ApplicationSets and mysterious AWS EKS Fargate nodes, resulting in some head-scratching, troubleshooting and interesting take-aways.
In this article:
 The Pull Request This merge should not create that many pods!? What happened?</description>
    </item>
    
  </channel>
</rss>