Scaling Up: Building a Bulletproof K3s Cluster on Proxmox I’ve been running services in my homelab for a while, but recently I hit a wall. I had a two-node Proxmox cluster that was supposed to be “High Availability,” but in reality, it was just a split-brain headache waiting to happen.
If you know anything about clustering, you know that two nodes is not a cluster. If one node goes down, the survivor doesn’t know if it’s the leader or if it’s isolated.
Troubleshooting Proxmox: When Simple Migrations Go Wrong I love my Proxmox cluster. It’s the beating heart of my homelab, hosting everything from my game servers to my media stack. But sometimes, what should be a simple click-of-a-button task turns into an hour-long troubleshooting rabbit hole.
Recently, I tried to migrate a VM from my primary node (pve1) to my secondary node (pve2). I’ve done this a dozen times before. I clicked “Migrate,” selected the target node, and waited for the magic to happen.
I recently built a new rig intended to serve two distinct functions. It needs to be a high-end gaming machine capable of crushing titles at 4K, but I also wanted it to serve as a headless inference node for my local LLM stack, powered by Ollama.
The challenge is balancing Power and VRAM.
My GPU, the Radeon RX 7900 XTX, features a massive 24GB of VRAM—excellent for local LLMs. However, high-end AMD cards can have high power draw at idle, and running an LLM server 24/7 on a “High Performance” power plan is inefficient.
