<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Simple Enough Blog</title><link>https://blog-dev.simpleenough.net/tags/kubernetes/</link><description>Recent content in Kubernetes on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 14 Jan 2026 13:45:30 +0200</lastBuildDate><atom:link href="https://blog-dev.simpleenough.net/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Test-Driven Infrastructure: Applying TDD to Infrastructure as Code</title><link>https://blog-dev.simpleenough.net/blog/infratdd/</link><pubDate>Wed, 14 Jan 2026 13:45:30 +0200</pubDate><guid>https://blog-dev.simpleenough.net/blog/infratdd/</guid><description>&lt;h1 id="test-driven-infrastructure" class="heading">Test-Driven Infrastructure&lt;a href="#test-driven-infrastructure" aria-labelledby="test-driven-infrastructure">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>




&lt;h2 id="applying-tdd-to-infrastructure-as-code" class="heading">Applying TDD to Infrastructure as Code&lt;a href="#applying-tdd-to-infrastructure-as-code" aria-labelledby="applying-tdd-to-infrastructure-as-code">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>&lt;strong>Test-Driven Development (TDD)&lt;/strong> is now well established on the application side.&lt;br>
However, when it comes to &lt;strong>infrastructure&lt;/strong>, many still consider TDD unnecessary, too complex, or unsuitable.&lt;/p>
&lt;p>That is a mistake.&lt;/p>
&lt;p>&lt;strong>TDD applied to infrastructure&lt;/strong> already exists, often without being named as such. When properly understood, it becomes a major lever for &lt;strong>securing, structuring, and evolving a cloud platform&lt;/strong>.&lt;/p></description></item><item><title>Karpenter: The Intelligent Autoscaler for EKS</title><link>https://blog-dev.simpleenough.net/blog/karpenter/</link><pubDate>Mon, 24 Nov 2025 11:18:06 +0200</pubDate><guid>https://blog-dev.simpleenough.net/blog/karpenter/</guid><description>&lt;h2 id="i-what-is-karpenter" class="heading">I. What is Karpenter?&lt;a href="#i-what-is-karpenter" aria-labelledby="i-what-is-karpenter">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>&lt;strong>Karpenter&lt;/strong> is an open-source autoscaler for Kubernetes, created by AWS.&lt;br>
Its purpose is to &lt;strong>automatically adjust the EC2 node capacity of an EKS cluster based on real workload demand.&lt;/strong>&lt;/p>
&lt;p>In short:&lt;/p>
&lt;ul>
&lt;li>When your cluster is short on resources, &lt;strong>Karpenter adds new nodes.&lt;/strong>&lt;/li>
&lt;li>When nodes become unnecessary, &lt;strong>it removes them.&lt;/strong>&lt;/li>
&lt;/ul>
&lt;p>But more importantly:&lt;/p>
&lt;p>It does this &lt;strong>faster&lt;/strong>, &lt;strong>more intelligently&lt;/strong>, and &lt;strong>more efficiently&lt;/strong> than Kubernetes’ traditional autoscaler (&lt;strong>Cluster Autoscaler&lt;/strong>).&lt;/p></description></item></channel></rss>