Topic

homelab

A collection of 15 issues

Systemd and Proxmox (Day 3)

It turns out that Proxmox’s quorum requirements are not as “simple” as I thought. The initial solution of setting quorum expectations to 1 worked… sort of. Here’s what happened: When a node booted up (remember it can’t initially “see” the other node), OPNsense would start (great!), provide

New Netgear Switch, OPNsense and Vlans (Day 2)

I got a new Netgear managed switch yesterday and so today was all about network segmentation and fighting with OPNsense. Also learned some interesting bits about Proxmox clustering that I didn’t expect to deal with. First up, got OPNsense reinstalled on the N100 box - fresh start for the

Terraforming Proxmox

So you've got Proxmox running, and you’re tired of clicking through the UI to create VMs. The next logical step is to write some provisioning code. This is how I did it. This was the first thing i did after installing the hypervisor, I went looking for

A highly available kubernetes home lab setup

Remember this single-control plane setup from last time? Well, I decided to level up. The New Architecture The plan is simple (this is an understatement): * 3 control plane nodes * 2 HAProxy load balancers with Keepalived for that sweet virtual IP All tied together with Tailscale for remote access Tailscale setup

Single control-plane Kubernetes home lab

So I decided to build a Kubernetes cluster at home. Sure, I could say it’s mainly for self-hosting + probably ML (I will need to add a GPU node) workloads I want to experiment with, but honestly, I’ve always wanted a homelab to tinker with. Having a proper test