I got tired of rebuilding my homelab Kubernetes cluster, so I automated the whol

<p>I wanted a Kubernetes lab that would still be there the next morning.</p> <p>A temporary cluster on my laptop would be useful for testing manifests, but it would disappear when

<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,

<p>In <a href="https://peculiarengineer.com/blog/kubernetes-first-app-k3s-single-node/" rel="noopener noreferrer">Part One</a> I deployed nginx on a single k3s node and killed a

<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>So we’ve already done a few things for setting up our own custom cluster. We’ve manually configured a Kubernetes Control Plane and joined worker nodes by hand. While that was a

<p>The Problem Nobody Talks About<br /> When I first approached Kubernetes, every tutorial assumed I was a developer coming from Docker. Nobody wrote for someone who knew vSphere

<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><a class="article-body-image-wrapper"