<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Spot on DevOps &amp; Rock&#39;N&#39;Roll</title>
    <link>https://artazar.pages.dev/tags/spot/</link>
    <description>Recent content in Spot on DevOps &amp; Rock&#39;N&#39;Roll</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Aug 2026 15:55:02 +0700</lastBuildDate>
    <atom:link href="https://artazar.pages.dev/tags/spot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Karpenter consolidation without the pager fatigue</title>
      <link>https://artazar.pages.dev/blog/11-karpenter-consolidation-spot/</link>
      <pubDate>Tue, 16 Jun 2026 00:08:30 +0000</pubDate>
      <guid>https://artazar.pages.dev/blog/11-karpenter-consolidation-spot/</guid>
      <description>&lt;p&gt;Karpenter&amp;rsquo;s consolidation is the feature that pays for the migration. It watches your cluster, notices that the workload fits on cheaper capacity, and rearranges the nodes to match. On a fleet running mostly spot, the savings are real and continuous — when I went through &lt;a href=&#34;https://artazar.pages.dev/blog/04-cutting-the-eks-bill/&#34; &gt;the cost optimisation exercise&lt;/a&gt;, it was one of the few changes that measurably moved the bill.&lt;/p&gt;&#xA;&lt;p&gt;It is also a machine that deliberately deletes your nodes, all day, forever. If your workloads aren&amp;rsquo;t ready for that, consolidation turns into a steady drip of alerts that eventually teaches everyone to ignore the alerting channel — which is a worse outcome than paying for the oversized nodes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
