undefined | Better HN

0 pointsoutime5y ago0 comments

K8s targets a long list of things that Nomad just doesn't want to deal with in the name of simplicity - and that's ok, if that suits your use case.

Some are mentioned in the post but I can think of secret management, load balancing, config management, routing, orchestration beyond workloads (e.g. storage), rollbacks/rollouts and many more. Perhaps in few areas there are some support but it's not what Nomad intends to do anyway. I also like these points from another comment: https://news.ycombinator.com/item?id=26142658

In order to supply those needs in Nomad you'll need to spend time finding out how to integrate different solutions, keep them up-to-date, etc. At that point, K8s may be a better answer. If you don't need any of those, use Nomad or anything else that's simpler (e.g. ECS if you're in AWS, K3s if that's simple enough for your home server, etc).

0 comments

stickupkid5y ago

> Some are mentioned in the post but I can think of secret management

Hashicorp Vault seamless integration.

> In order to supply those needs in Nomad you'll need to spend time finding out how to integrate different solutions, keep them up-to-date, etc

Like how k8s secrets are secure out of the box ?

outimeOP5y ago

I can understand how they seamlessly integrate with their own products (and I like Vault a lot) - not sure how it'd work with other secret backends if you'd prefer them over Vault. It's also fine you picked an individual item of a long list to rebut what I said. But this is what I said:

>Perhaps in few areas there are some support but it's not what Nomad intends to do anyway

Look, I think we can agree that K8s have many features that Nomad don't and that's just how it is (not good or bad, just different). This comes with added complexity. If you wanted to have all these features in Nomad it'd cost you a lot to the point of being impractical. "I don't need all of those" then don't use K8s - but then don't complain when you bring a vast machine that does 1000 things to do 100 and complain it's too complex.

sofixa5y ago

> of secret management, load balancing, config management, routing, orchestration beyond workloads (e.g. storage), rollbacks/rollouts

Nomad does all of these either natively ( rollbacks/rollouts) or via external tooling ( Vault, Consul, a load balancer). Unix philosophy and all that, and besides, Kubernetes doesn't do load balancing, and secret management is a joke.

Aeolun5y ago

If it does these things through external integrations, it’s not really something Nomad does.

sofixa5y ago

By that logic, Kubernetes does nothing that is offloaded to operators, CRDs, CSI plugins, etc. The fact that you can extend it with extra features and it supports that is kinda doing something.

j / k navigate · click thread line to collapse

0 pointsoutime5y ago0 comments

K8s targets a long list of things that Nomad just doesn't want to deal with in the name of simplicity - and that's ok, if that suits your use case.

0 comments

stickupkid5y ago

> Some are mentioned in the post but I can think of secret management

Hashicorp Vault seamless integration.

> In order to supply those needs in Nomad you'll need to spend time finding out how to integrate different solutions, keep them up-to-date, etc

Like how k8s secrets are secure out of the box ?

outimeOP5y ago

>Perhaps in few areas there are some support but it's not what Nomad intends to do anyway

sofixa5y ago

> of secret management, load balancing, config management, routing, orchestration beyond workloads (e.g. storage), rollbacks/rollouts

Aeolun5y ago

If it does these things through external integrations, it’s not really something Nomad does.

sofixa5y ago

By that logic, Kubernetes does nothing that is offloaded to operators, CRDs, CSI plugins, etc. The fact that you can extend it with extra features and it supports that is kinda doing something.

j / k navigate · click thread line to collapse