Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Running Nomad for a Home Server

mrkaran.dev

Post reply on HN
Print view View original

121–130 of 153 posts

Re: Running Nomad for a Home Server

#121

Post by chrischen »

ForHackernews wrote: post #70
throwaway894345 wrote: post #62

Earlier quoted context omitted.

I would be very interested in a more detailed write-up on Nomad vs Kubernetes for bare metal. I'm working through getting Kubernetes stood up, but I'm running into a dearth of features--namely you have to bring your own load balancer provider, storage provider, ingress controller, external DNS, monitoring, secret encryption, etc, etc before you can run any real world applications on top of it. I would be interested i…

I'd be really interested, too. Have you looked at k3s at all? We're considering trying to run https://github.com/rancher/k3os on bare metal servers.

Any thoughts on RKE which runs a full k8s distro? Was able to deploy bare metal with just a single cluster config and “rke up”.

Re: Running Nomad for a Home Server

#122

Post by t0astbread »

superkuh wrote: post #43

Why would you run Nomad for a home server? This isn't for home server use. This is for practicing skills only required in commercial environments. Skills you only have a need for because someone pays you: because it's not fun and stupid. Taking that process home and doing all that instead of just running nginx from your distro repos on the sbc OS is cargo cult insanity for 99% of cases.

I guess the #1 reason to run Nomad on your home server is "because you're interested in it". Which is also probably the #1 reason to run a home server to begin with, for most people.

Also, while I don't wanna dispute the effectiveness of it, you should evaluate if "just running nginx from your distro repos" is fine under your threat model when you start exposing stuff to the internet or start introducing services that handle personal information.

Re: Running Nomad for a Home Server

#123

Post by throwaway894345 »

dilyevsky wrote: post #112
throwaway894345 wrote: post #97

Earlier quoted context omitted.

Yes, to be clear, these problems can be worked around (although many such workarounds have their own tradeoffs that must be considered in the context of the rest of your stack as well as your application requirements); I was observing that the defaults are not what I would consider to be production-ready.

I don’t think kubernetes ever promised to be a turnkey system at least outside of cloud. There are many commercial vendors though willing to fill that gap.

> I don’t think kubernetes ever promised to be a turnkey system

No one is arguing that they did.

Re: Running Nomad for a Home Server

#124

Post by CGamesPlay »

tetha wrote: post #59

We're pulling the trigger tomorrow to migrate the first productive system to nomad, and launch 1-2 new products on nomad first. It's quite exciting. We chose nomad there, because it's a business requirement to be able to self-host from an empty building due to the data we process - that's scary with K8. And K8 is essentially too much for the company. It's like 8 steps into the future from where most teams in product…

This is off-topic trivia, but since it's clear it wasn't a typo: it's "k8s", not "k8", and it originates from "kubernetes" having 8 letters between "k" and "s". Similar to "a11y" ("accessibility") or "i18n" ("internationalization") or "a16z" ("andreessen horowitz").

Re: Running Nomad for a Home Server

#125

Post by fomine3 »

throwaway894345 wrote: post #123
dilyevsky wrote: post #112

Earlier quoted context omitted.

I don’t think kubernetes ever promised to be a turnkey system at least outside of cloud. There are many commercial vendors though willing to fill that gap.

> I don’t think kubernetes ever promised to be a turnkey system No one is arguing that they did.

Obviously original authors want users to use their cloud.

Re: Running Nomad for a Home Server

#126

Post by fomine3 »

mad_vill wrote: post #41
marvinblum wrote: post #21

I did/do run both myself, Kubernetes and Nomad, and it was a million times easier to set up Nomad (including Consul) on bare metal than it was to set up Kubernetes. Kubernetes offers more features, but you most likely don't need them and the increase in complexity makes it a pain to maintain. I'm running a three-node cluster on Hetzner [0] for Pirsch [1] right now and haven't had any difficulties whatsoever when upgr…

bear metal sounds so sick. I'm in for an industrywide rename :D.

It's sold as Thermal Grizzly Conductonaut

Re: Running Nomad for a Home Server

#127

Post by 3np »

CGamesPlay wrote: post #124
tetha wrote: post #59

We're pulling the trigger tomorrow to migrate the first productive system to nomad, and launch 1-2 new products on nomad first. It's quite exciting. We chose nomad there, because it's a business requirement to be able to self-host from an empty building due to the data we process - that's scary with K8. And K8 is essentially too much for the company. It's like 8 steps into the future from where most teams in product…

This is off-topic trivia, but since it's clear it wasn't a typo: it's "k8s", not "k8", and it originates from "kubernetes" having 8 letters between "k" and "s". Similar to "a11y" ("accessibility") or "i18n" ("internationalization") or "a16z" ("andreessen horowitz").

I assumed it was a typo but I like it. I’ll start calling it Kate.

Re: Running Nomad for a Home Server

#128

Post by mr-karan »

sofixa wrote: post #73
omneity wrote: post #46

Earlier quoted context omitted.

Yeah, when making the decision it was quite harrowing to think of maintaining a cluster in production. Nomad had very little operational complexity compared to what we imagined. We've had two main outages in months: - Server disks were filling up and we hadn't set up monitoring properly at the time (ironic for the name of our company :) ). Not Nomad's fault. - A faulty healthcheck caused all the servers of a cluster…

Jaeger is pretty great for tracing, and can integrate with Traefik/Envoy ( or whatever you use for ingress/inter-service communication). We're running Loki for the logs ( via nomad log forwared/shipper and promtail) and so far it's going great. I'll have to do a write-up about the the whole thing.

I'd love to see your write-up on thr logging thing. Please do!

Re: Running Nomad for a Home Server

#129

Post by mr-karan »

bbss wrote: post #35

> host_network as of present cannot bind to a floating IP address (DigitalOcean/GCP etc). I've to resort to using my droplet's public IPv4 address for now. You should be able to bind to the anchor ip to make the floating ip work. https://www.digitalocean.com/docs/networking/floating-ips/ho...

Author here.

Thank you for the tip. I'll try it out.

Re: Running Nomad for a Home Server

#130

Post by [deleted] »

sneak wrote: post #58
0xbadcafebee wrote: post #17

Earlier quoted context omitted.

> Wish we’d all agree to one templated configuration format. If you mean a standard configuration file format, that has almost never happened in the entire history of computing. There are standard data formats , sure, but to standardize a configuration file, all the applications need to be limited to the functionality expressed in a single config file format. Most applications hate that, because they want to add infi…

There was pretty broad ad hoc standardization in dos/windowsland on the ini-file format, which was broadly formalized as toml years later.

[deleted]
Post reply on HN