I later realised my blog and little side projects do not need a cluster but that's another story. I was mainly looking at it to learn than to properly utilize
Completely off topic, sorry. Whatever happened to Flynn.io? That was my favorite of the clustery things but it just sort of fell off the internet
e: oh. Answered by visiting the site just now. "Flynn is no longer being developed." that is a shame.
It's gotten drastically better, but updates are still serious work ( point in case, all cloud providers bar Scaleway are usually multiple versions late)
... will build deep understanding and accumulate knowledge over the years. I won't deny that you could learn Nomad fast, but becoming an expert in some domain really takes some time.
I don't entirely know if this joke matches the reality of Nomad vs K8S, but that's probably the general sentiment. Bigger usually implies harder to fix.
To be fair, this time around the ones afraid of Kubernetes are the companies trying to sell a Kubernetes competitor.
I just used Kubernetes at work, inherited a poorly maintained cluster, and when time came to change, due to very limited time available, we opted for Nomad. Few years in, i'm telling what i've learned ( while still running a k8s cluster for home use, so i'm not entirely disconnected from the k8s ecosystem)
However one of the things I jumped into the assumption that the blog post was stealth advertising for Nomad was a few exaggerated claims that feel quite a stretch to be able to come up with anything in favour of Nomad over Kubernetes.
One of them, for example, is that
Nomad is supposed to be "significantly easier than microk8s or minikube or kind" to run locally as a dev environment. Well, anyone familiar with minikube is well aware that to get it up and running you only need to install it and kubectl, and quite literally just run 'minikube start'. Nomad agent is not only far more convoluted to get up and running according to Nomad's official documentation, but it is also explicitly stated that it's use is highly discouraged. Don't you feel that you're misrepresenting Nomad's selling points?
> Nomad is supposed to be "significantly easier than microk8s or minikube or kind" to run locally as a dev environment. Well, anyone familiar with minikube is well aware that to get it up and running you only need to install it and kubectl, and quite literally just run 'minikube start'
It would appear that i wasn't up to date on minikube - last time i installed it ( it was a few years back, and since then i've switched to microk8s for local stuff), it required a VM intermediary and driver, but that's no longer the case, direct Docker being supported. That's drastically easier than it was before, but there's still a slight advantage to Nomad (see below).
> Nomad agent is not only far more convoluted to get up and running according to Nomad's official documentation, but it is also explicitly stated that it's use is highly discouraged
How so? Download a binary, run `nomad agent -dev` and that's it, there's nothing convoluted. It's highly discouraged the same way minikube is - for production use. With `nomad agent -dev` you get a local ephemeral Nomad instance you can do whatever you want with, but should never use it for production use.
The small advantage i talked about is that minikube is a separate thing you have to download ( and there's minikube vs microk8s vs kind); with nomad, it's the same one as the CLI you need to interact with the cluster. So i'd be like there was `kubectl minikube start`, and that's it - you can go from working with a cluster to having a local one for testing in a command. Very slight advantage, indeed, but still one IMHO.