3 ms·

I've run into so many issues with Nomad that it really doesn't make sense to compare the two. Many are well documented in Github issues and occur when utilizing

• numbsafari 5y ago
  I'm curious how responsive you have found them to issues you've identified. Any particular problems you've experienced that have been long standing an unresolved? I occasionally like to kick the tires on Nomad, but so far haven't found it compelling enough to switch away from my current solution, GKE (mostly because of how integrated it is with everything else I am doing and, at this point, familiarity). So, curious to hear from others where the rough edges are.
  • 3np 5y ago
    Not the person you’re replying to, but I’m a couple of years in on Nomad, coming from kubernetes. I’ve reported and participated in a few issues. Most got fixed within the next couple of minor versions, some went neglected. I think the somewhat recent 1.0-release was pretty well-timed. There are still a few rough edges (though it’s gotten a lot better continuously over than last year). Specifically, Consul Connect and federation (especially together with ACLs and mTLS) are just about coming together now. If you don’t rely on Connect and federation across regions, I’d say it’s reliable for production use. Other than that maybe wait 6-12 months and reassess. I’d also advise to put ACLs and TLS in place before you start putting production loads there; it’s not great to introduce in a running cluster.