<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scaling on Nerdsid.com</title><link>https://nerdsid.com/tags/scaling/</link><description>Recent content in Scaling on Nerdsid.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 29 Aug 2026 17:00:00 +0000</lastBuildDate><atom:link href="https://nerdsid.com/tags/scaling/index.xml" rel="self" type="application/rss+xml"/><item><title>CKA Prep: Creating And Manually Scaling A Deployment</title><link>https://nerdsid.com/posts/creating-and-manually-scaling-a-deployment/</link><pubDate>Sat, 29 Aug 2026 17:00:00 +0000</pubDate><guid>https://nerdsid.com/posts/creating-and-manually-scaling-a-deployment/</guid><description>&lt;p>A Deployment can be created in an instant, but that doesn’t mean it’s ready to use. In this lab, the Deployment still showed 0/2 available 81 seconds after creation. Nothing was broken. The worker node was simply pulling the image for the first time. If you treat the created message as confirmation that everything is ready and move on, you can end up debugging a problem that doesn’t actually exist.&lt;/p></description></item></channel></rss>