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

Nomad vs. Kubernetes

nomadproject.io

Post reply on HN
Print view View original

351–360 of 369 posts

Re: Nomad vs. Kubernetes

#351

Post by GordonS »

sofixa wrote: post #264
glynnforrest wrote: post #61

> Flexible Workload Support This is Nomad's most underrated feature, IMHO. You don't have to use containers for everything if you don't want to. For example, if you're a golang shop you can run everything as native binaries and cut out docker completely. Nomad has much simpler networking, i.e. no web of iptables rules to figure out. You can add Consul connect as a service mesh if you need it, but if you don't, you ca…

> The main downside for me is a lack of plug and play pieces, Hashicorp just announced Nomad Packs filling that precise niche. Still in beta, and it was a long time coming but IMHO it was the main thing missing and is honestly awesome.

I looked into Nomad a whole back, and finding good examples was a problem - Packs looks fantastic!

Re: Nomad vs. Kubernetes

#352

Post by GordonS »

marvinblum wrote: post #33

I've been running a production-grade Nomad cluster on Hetzner for the past 1 1/2 years and it's fantastic. It was amazingly easy to set up compared to Kubernetes (which I also did), the UI is awesome, updates haven't broken anything yet (as long as you follow the changelog) and it's stable. I really like the separation of concerns the HashiStack offers. You can start out just using Consul for your service meshing, an…

I'm really curious about the local development story for Nomad.

I'm using Docker Swarm in production, which let's me easily spin up the same services locally as I do for production - it's really nice to have one set of yaml files that can be used across all environments, and of course it gives more confidence before shipping to prod.

How do you handle local development? Do you have Docker Compose files specifically for that, or something else?

Re: Nomad vs. Kubernetes

#353

Post by Jedd »

glynnforrest wrote: post #232
Jedd wrote: post #147

Earlier quoted context omitted.

This has been my biggest pain point - world+dog shares their helm charts, but blog posts or git*.com repos with non-trivial cluster recipes are rare. f.e. We're exploring cortexmetrics currently, and spinning the full stack version up on k8s (openshift) was straightforward. Porting all that spaghetti onto nomad would be a huge job, though part of the frustration is knowing someone, tucked away on a private network, h…

> the frustration is knowing someone, tucked away on a private network, has already done this. Hard agree. I know this person and have been this person before. I've toyed with the idea of writing a book of Nomad recipes and tips, I wonder if anyone would read it? Also, watch this space, helm for Nomad may be coming soon: https://github.com/hashicorp/nomad-pack

A book - probably not so much.

The big value of sites (mostly github master repos) that offer recipes for saltstack/chef/ansible/puppet, or the helm collective, etc - are that they're continually being tweaked as new versions of (upstream) software are released.

They usually all require a fair bit of localisation before they 'just work', at least in my experience, but the template taken from a proven functioning system, and then abstracted & shared, is worth its weight in gold.

I've set up a few nomad jobs, but nothing anywhere as complex as, say, this cortexmetrics monstrosity. Even our k8s & nomad guru baulks at such an undertaking.

Re: Nomad vs. Kubernetes

#355

Post by dstrickland »

sofixa wrote: post #264
glynnforrest wrote: post #61

> Flexible Workload Support This is Nomad's most underrated feature, IMHO. You don't have to use containers for everything if you don't want to. For example, if you're a golang shop you can run everything as native binaries and cut out docker completely. Nomad has much simpler networking, i.e. no web of iptables rules to figure out. You can add Consul connect as a service mesh if you need it, but if you don't, you ca…

> The main downside for me is a lack of plug and play pieces, Hashicorp just announced Nomad Packs filling that precise niche. Still in beta, and it was a long time coming but IMHO it was the main thing missing and is honestly awesome.

Here's the repo link in case you need it for Nomad Pack. https://github.com/hashicorp/nomad-pack

Re: Nomad vs. Kubernetes

#356

Post by dstrickland »

xtat wrote: post #354

I was into it until I saw there is an enterprise version link. If it's not FLOSS I'm out.

It's mostly OSS. There are pay to play enterprise features, but you can most definitely run high end production clusters without needing enterprise.

Re: Nomad vs. Kubernetes

#357

Post by proxysna »

mkopinsky wrote: post #194
proxysna wrote: post #115

Earlier quoted context omitted.

You should be ok with consul, ansible and templating your docker-compose files. Might take some time to set it all up, but should be ok.

Thanks for the suggestion. Any suggested starting points for my research? DDG search for "ansible docker-compose" brings up some suggestions like [1] and [2] but I'm curious if you have other suggestions. And just so I understand how these work together - I'd use Jenkins+ansible to push containers to my servers, I'd run consul within docker as well, and ... would Ansible register services with consul as it pushes the…

Missed the whole consul part of the question. To register services you can: 1. You can use ansible module [0] 2. Use a template to create json files or suing http API [1] 3. Registrator. Project is old but still works well. [2]

> Do the services need to be modified to speak with consul directly?.

I am not sure that i get you, but had no such need when migrating legacy stuff.

[0] https://docs.ansible.com/ansible/latest/collections/communit... [1] https://learn.hashicorp.com/tutorials/consul/get-started-ser... [2] https://github.com/gliderlabs/registrator

Re: Nomad vs. Kubernetes

#358

Post by dikei »

scns wrote: post #154
dikei wrote: post #106

Earlier quoted context omitted.

> How do you do networking? Layer a service mesh with custom overlay networking that abstract upon k8s clusterip. Overlay network is easy if you don't need your pod and service IP to be routable from outside the cluster. It took me less than 1 afternoon to learn to use Kubespray to deploy an on-premise cluster with Calico for overlay network.

Zero snark, but you confirm parent somehow IMHO. Two more tools.

Well, Kubespray is just an Ansible-based installer that almost walk you through the process of setting up a K8S cluster. And Calico is the default option in Kubespray, so unless you want more customization, you don't need to learn anything about it.

Re: Nomad vs. Kubernetes

#359

Post by hnlmorg »

pdimitar wrote: post #40
hnlmorg wrote: post #24

Earlier quoted context omitted.

I've had just as many problems maintaining mature C++ projects as I have maintaining mature Go projects. Ultimately it all boils down to two things: - The projects being well written and well maintained from the outset - Personal preference I cannot overstate that second point. It really is about time developers stopped pushing their own personal preferences as if it's some kind of fact.

> It really is about time developers stopped pushing their own personal preferences as if it's some kind of fact. Agreed, so let's all go to Rust or OCaml because they have very strong static typing systems. ;) Both C++ and Go have plenty of warts, with C++ having way too many footguns and Go allowing you to use it as a dynamic language whenever you figure it's too much work to go through your problem with static typ…

You've very much missed the point of my post. But from the tone of your reply, I sense we'd never see eye to eye anyway.

Re: Nomad vs. Kubernetes

#360

Post by neop1x »

sciurus wrote: post #281
llama052 wrote: post #273

Earlier quoted context omitted.

A lot of the cloud providers don't bill directly for kubernetes management, instead it's just the node resources. Either way, as another comment points out, Rancher and many other solutions make the orchestration of creating your own Kubernetes cluster really boring. We run a few kubernetes clusters on premise, and for the longest time it was just 1 person running some Kubernetes clusters.. we even have other teams i…

Which cloud providers don't? I'm only familiar with AWS and GCP, and they both have a base hourly charge per-cluster.

Scaleway
Post reply on HN