homelab - Nomadin

Nomadin

homelab

A collection of 10 posts

Storage (TrueNas, and USB controllers) (Day 13-15)

100daysofhomelab

Storage (TrueNas, and USB controllers) (Day 13-15)

What started as needing storage turned into a deep dive into USB and storage performances, and lessons about things like UASP, unstable drive paths, and temperamental USB controllers.

Service Routing with Traefik - External Services and URLs (Day 9)

100daysofhomelab

Service Routing with Traefik - External Services and URLs (Day 9)

Using Traefik to route traffic to services outside Kubernetes, e.g. Proxmox and OPNsense UIs, including SSL certificates.

Complex Simple Solutions Continued (Day 7)

Complex Simple Solutions Continued (Day 7)

This is a continuation of the previous post here. Left off with the Traefik setup in k3s not picking up the certificate, and if you read that post one thing that immediately comes to mind is “Did you check the right TLS secret was being used?” Since I’m working

Complex Simple Solutions (Day 5 & 6)

Complex Simple Solutions (Day 5 & 6)

After the whole VM boot ordering not working the way i wanted, I finally decided to uncluster the nodes. (Also very likely a skill issue). To be fair having the nodes in a cluster made it easier for centralized management and easy VM migrations. From LXC to K3s This is

Traefik, Reverse Proxies and Lxc Containers (Day 4)

Traefik, Reverse Proxies and Lxc Containers (Day 4)

After running Proxmox for about 2 months, I realized I hadn’t tried out LXC containers yet. What better way to start than setting up a reverse proxy? What’s a Reverse Proxy? Think of a reverse proxy like a bartender - you ask for a drink, and they handle

Systemd and Proxmox (Day 3)

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)

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

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

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

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