this post was submitted on 28 Jan 2024
44 points (95.8% liked)

Selfhosted

40296 readers
212 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I've gotten to the point where I have more than a few servers in my homelab and am looking for a way to increase reliability in case of an update. Two problems: 2 of the servers will be on Wifi and one is a Synology NAS. I can't do any wiring but I can put together a WiFi 6E network for the servers only, That means buying 4 Wifi 6E devices in a mix of types. As for Synology, it's container manager is a little odd so I expect to run a Linux VM and use that as my cluster node. That may mean buying more RAM as I haven't upgraded it. Hardware ranges from a 6 core CPU on the NAS (with a few important docker containers), 8 core on my main SFF server (which also runs my OpnSense VM inside Proxmox), 16 core Ryzen on my old big server, and a 10 year old NUC for fun. So the question is what do I use to orchestrate all the services I have. My Vaulwarden runs reliability but only on one system. I want better reliability for Pihole that automatically syncs settings. The NAS' docker implementation doesn't support gravity sync. Since everything I do runs in docker besides storage it seems Proxmox clusters is not the best option. That puts me between K8s and Docker Swarm. I'd like something that is simple to administer but resilien when hardware fails.

you are viewing a single comment's thread
view the rest of the comments
[–] iluminae@lemmy.world 3 points 9 months ago (2 children)

I use k8s at work a lot - I choose to use Nomad at home, you may want to add that to your shortlist.

[–] jelloeater85@lemmy.world 1 points 9 months ago (2 children)

How you liking it? Seemed a little hard to learn to me, and I do TF and Ansible.

[–] 1984@lemmy.today 2 points 9 months ago

I thought it was quite simple but it depends on your experience of course. It's a single binary and a single config file, so I felt it was soo much simpler.

You can buy a good udemy course for 10 dollars too which really helps in the beginning.

[–] iluminae@lemmy.world 1 points 9 months ago

Yea it's very easy to learn enough to run, it has built-in service discovery and secrets now, and writing parameterized jobs feels so much nicer than a helm chart in k8s.

10/10, would orchestrate again

[–] diminou@lemmy.zip 1 points 9 months ago

Thank you for Nomad, will give this one a try at home!