Hacker News new | ask | show | jobs
by jitl 3056 days ago
You need containers to run on Kubernetes my dude. And running on Kubernetes is critical.
4 comments

Yes I know you were being sarcastic.

But you don't need k8s or containers for orchestration.

I chose Hashicorp's Nomad (I'm the dev lead for our company) precisely because I didn't want to commit to Docker from day one but I did want to leave that option open. Nomad works with everything - Docker containers, jar files, shell scripts, raw executables, etc and is dead simple to set up - one < 20Mb self contained executable that works as a client, server and as a member of a cluster. Configuration is dead simple if you use Consul.

Reminds me of this: http://www.mongodb-is-web-scale.com/

"Docker, docker, docker!"

Edit: I'm not knocking either of these products - I actively use Mongodb in production. I like docker/containers/Kubernetes and have used them for various projects. I just take offence with how people have started ignoring common sense, like: we don't have the tooling in place to support this product, or: it doesn't meet our business needs.

I think orchestration is critical. Kubernetes has obviously "won", but we're getting alot of wins from running on ECS that we'd have to rollback and reimplement on K8S, at least until EKS becomes available.

(honestly couldn't tell if you were being sarcastic, so assumed you weren't)

If you aren't currently struggling to manage a large pool of servers / services, then you don't need Kubernetes. Not yet, at least. It's over-complicated overkill if you don't need it yet. So are containers, actually, but the bar is a lot lower for them.