this post was submitted on 27 May 2024
22 points (95.8% liked)

homelab

6596 readers
6 users here now

founded 4 years ago
MODERATORS
 

Hi, so I have a very individual homelab. It's a collection of stuff accumulated over nearly 30 years of doing weird stuff.

For the past 9 years it's been running as a bunch of lxc containers (privileged because unprivileged did not exist, back then) but several of those containers are p2v conversions of physical hosts dating back to debian woody and earlier. They're all upgraded to at least buster, most are bookworm. Stuff like asterisk, email, home assistant, nextcloud, matrix synapse run there these days.

The server is a 15 year old HP gen6 thing, and is getting quite long in the tooth. There's also a dedicated cheapy microserver with an i4 running opnsense on bare metal as a firewall.

Trying to run stuff like local voice stuff for home assistant is showing the HP's age quite badly. Also, our area is getting fibre, and the opnsense box is maxed out at gigabit. More speed would be nice.

So, I'm in two minds. The homelab has been a lot of fun over the years, but I'm over 50 now, I want lower maintenance. This latest wave of upgrades is making me rethink the next 20 years of homelab. I don't want to leave something stupidly "only me" if I were to die tomorrow (diabetes is a fickle bastard). My wife might want to try and carry on this thing - it runs some useful stuff around the house (but it should be noted that nothing in this house requires a server or cloud) - and that's not going to happen with the current solution.

I think I might have a path, using proxmox, from where I am now, to something that can be deployed on e.g. a bunch of ms01 class devices. I'm thinking to convert the existing HP server to proxmox, to allow me to redeploy all my existing lxc containers into the proxmox world. As I acquire hardware over the next year, I can look at a k8s migration of the services onto a small, MUCH lower power cluster. One of the keys is that I don't want to have big outages of services for days or weeks while I migrate everything so it's gotta be a rolling upgrade as it were.

I'm here soliciting feedback. Has anyone ever migrated from a deeply legacy homebrew homelab into something like this? Does it reduce the workload long term? What's the practicality of this for someone rather less tech savvy?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] orb360@lemmy.ca 1 points 5 months ago

All the images I used already had x86 variants available. In fact, I was building and pushing my own arm variants for a few images to my own Nexus repository which I've stopped since they aren't necessary anymore.

If you are using arm only images, you'll need to build your own x86 variants and host them.

I created a brand new cluster from scratch and then setup the same storage pv/PVCs and namespaces.

Then I'd delete the workloads from the old cluster and apply the same yaml to the new cluster, and then update my DNS.

I used kubectx to swap between them.

Once I verified the new service was working I'd move to the next. Since the network storage was the same it was pretty seamless. If you're using something like rook to utilize your nodes disks as network storage that would be much more difficult.

After everything was moved I powered down the old cluster and waited a few weeks before I wiped the nodes. In case I needed to power it up and reapply a service to it temporarily.

My old cluster was k8s on raspbian but my new one was all Talos. I also moved from single control plane to 3 machines control plane. (Which is completely unnecessary, but I just wanted to try it). But that had no effect on any services.