Misadventures in Kubernetes: Autoscaling Workers

<p>So we have built a control plan from scratch. That’s kinda useful and was also kinda hard to make? But, really what we want to make is a proper, functioning, multi-node cluster

<p>When using managed platforms like Google Kubernetes Engine (GKE), there are many things that you don’t have to worry about that it takes care of for you! But have you ever

<p>Most of us run <code>kubectl apply -f</code> dozens of times a day without thinking about the machinery it sets in motion. But when something breaks, a Pod stuck in

<p>Disclaimer: this is not a post from a seasoned DevOps engineer. So if you also know very little about Kubernetes, ignorance loves company.</p> <p>To start with some (somewhat)

<p><a class="article-body-image-wrapper"

<p><a class="article-body-image-wrapper"

<p>Kubernetes Concepts are not random; each one has a beautiful problem-solving story behind it. </p> <p>Most people learn Kubernetes the wrong way.</p> <p>They see it as a list

<p>Most homelab content stops at "I installed Proxmox on a NUC." This post goes further — how I built a multi-node cluster running a full Kubernetes platform with GPU inference,