<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mks on A cup of coffee</title><link>https://a-cup-of.coffee/tags/mks/</link><description>Recent content in Mks on A cup of coffee</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2026</copyright><lastBuildDate>Sun, 12 Jul 2026 21:10:35 +0200</lastBuildDate><atom:link href="https://a-cup-of.coffee/tags/mks/index.xml" rel="self" type="application/rss+xml"/><item><title>Karpenter + Cluster API</title><link>https://a-cup-of.coffee/blog/karpenter-capi-ovh/</link><pubDate>Sun, 12 Jul 2026 03:18:18 +0200</pubDate><guid>https://a-cup-of.coffee/blog/karpenter-capi-ovh/</guid><description>One of Kubernetes&amp;rsquo; great strengths is being able to manage our resources elastically. If a stateless pod consumes too much, we can add replicas; if it has irregular consumption, we slap an HPA (Horizontal Pod Autoscaler) on it and it adapts to the load. Our cluster is full? We can add nodes to it.
But while autoscaling replicas is automatic, doing the same for nodes isn&amp;rsquo;t necessarily trivial.
In my article about the Cluster API, I ended on a little teaser:</description></item></channel></rss>