My homelab is essentially my own passion project and only really I access it except for when I spin up the occasional game server for friends.

I'm currently running Proxmox and run a debian LXC container for each docker stack I have, and have OpnSense routing incoming traffic with Haproxy with ssl offloading. My currently running LXCs are: mediawiki, amp game server(2 Minecraft servers), freshrss, and currently playing around with n8n.

I'm looking to collapse my LXC's to just VMs. I'd like to be able to have 3 VMs running in a Docker Swarm together so I can upgrade a VM at a time and just swing my running containers to another docker node and then swing back when the VM is stable again.

I've looked at k0s, k3s, and k8s and it just seems way too much work and overhead for what I'm willing to do. I also want to keep using docker compose and want a decent webgui to manage my containers/nodes/swarm. I'm using DockHand right now, but need to research swarm support.

Anyone have any advice for something like this? Any specific terms, tech, software I should look into?

Also, gonna throw a curveball, but what would the effects be of running 3 different distros as my nodes in my swarm? Like a Debian node, Rocky Linux node and potentially arch node? I'm guessing I shouldn't due to docker engine differences potentially.

I'm just trying to have fun with things, break things, fix them, learn, etc.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 5 months ago

It's not that I'm adverse to learning something new, it's just that I have limited time in my day-to-day currently, and while I'm looking to replace my existing structure with something new, I have to take into account my time that is available.

Kubernetes is definitely the "end goal" for some and potentially myself, but looking at the wall of knowledge for that and needing to learn it piecemeal with my current free time, it'll probably take me a month or more to get stable and document it for myself and I was hoping for something faster than that.

For example my pfsense VM that I was running previously, that I've been running for 5-6 years now, recently went corrupt due to a power outage. Kernel panics, corrupt file system warnings, sometimes the VM would boot and sometimes not. So I had my backup configs and figured maybe now is the time to switch to opnsense. Well that took me a week to figure out because I could only spend 1 hour a night on it, and I'm still not finished with it but I'm 90% there and have put a pin in it.

So yes I do want to learn and expand my skillset for my career, but Kubernetes I think is just not the right thing for me at this exact moment. I'm still looking into it and haven't decided on what I'm going with yet, but so far information feels very scattered on it.

  • source
  • parent