Hacker News Reader

Comment by themgt | Hacker News Reader

Nomad seems to be a truly "lightweight Kubernetes"

k3s requirements: 1 node, 512MB RAM, 1 CPU core

Nomad requirements: "Nomad servers may need to be run on large machine instances. We suggest having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of fast disk and significant network bandwidth."

https://docs.k3s.io/installation/requirements

https://developer.hashicorp.com/nomad/docs/install/productio...

View on HN

Hashicorp is playing safe here, Nomad can do with far far less resources.

That can be said of many systems, does hashicorp document it though? I’m guessing they must, otherwise that would be the first thing you hear on the other side of a support call.

also with hashicorps new licensing regime...

That does not impact 99% of ppl..

The licence change impacts only companies like Digger or Spacelift that build their platform abusing TF oss offering.

That's a bad take and you know it. HashiCorp couldn't make money because their enterprise offering was slim on features and overpriced. Rather than compete, they're playing protect-the-castle with some aggressive plays to keep their company afloat. They're bad stewards of open source (always have been) and are now getting their just desserts.

You can say the same about MariaDB, Elasticsearch, CocroachDB etc.

Why is „AWS attacks OSS” bad and „Spacelift attacks OSS” good ?

Its exactly the same case just size of companies is different.

This is for large deployments in prod. Nomad and Consul servers at home are running on an old Rpi3 with 2G of ram managing several devices and about 10 vm's. Larger deployment of ~30vm's was managed with a nomad/consul cluster of 3x2cpu4ram with no issues.

Reply on news.ycombinator.com