<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hpa on TheBigHouse</title><link>https://thebighouse.nl/tags/hpa/</link><description>Recent content in Hpa on TheBigHouse</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thebighouse.nl/tags/hpa/index.xml" rel="self" type="application/rss+xml"/><item><title>Busy evenings: scaling your application</title><link>https://thebighouse.nl/writing/k8s-04-busy-evenings/</link><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><guid>https://thebighouse.nl/writing/k8s-04-busy-evenings/</guid><description>&lt;p&gt;Give your application more Pods when things get busy, then let Kubernetes adjust the numbers.&lt;/p&gt;&#10;&lt;p&gt;A quiet evening in the house becomes a party. Two people handling drinks were plenty an hour ago. Now there&amp;rsquo;s a queue in the hallway. Getting a few more people to help is usually easier than asking those two to move six times faster.&lt;/p&gt;&#10;&lt;p&gt;Your application can work the same way. A Deployment can run several copies of a Pod, called replicas. Adding replicas is horizontal scaling. A Service sends traffic to the ready Pods behind it, so callers keep using the same address as the numbers change.&lt;/p&gt;</description></item></channel></rss>