Nomad can do everything that K8s can

I stopped reading when the solution for DNS was AWS and the solution for stateful sets was AWS EC2.<p>This is just a very weird comparison. Seems like the author doesn’t understand why people run K8s.<p>Of course they also “managed” several k8s clusters using… wait for it… AWS.<p>I’d say, when you are all in AWS, then fine don’t use k8s. But you also don’t need Nomad then in most cases.<p>And if you do need nomad on AWS then that’s fine as well, but it’s not comparable to k8s in general.

I’ve always hated this style of argument in tech where someone says X <i>can</i> do what Y does as an argument against using Y (or for using X) because it always missed *why* people use Y in the first place.<p>See for example you can write safe code in C therefore rust is pointless (yes but rust makes it much easier to write safe code)<p>Or you can do machine learning in JavaScript so python is useless (you can but it’s a much smaller ecosystem)<p>Etc etc.<p>You can pick whatever tools you want for whatever reason but please give me a better reason than it *can* be done.

I wish more places ran Nomad. I haven&#x27;t used it myself but it seems so much simpler than Kubernetes (and, like the author, I have extensive experience operating Kubernetes clusters) and HCL is a dream compared to drowning in OpenAPI docs and Golang structs to figure out how the hell to define the MySuperCoolCR resource that x.y.x-k8s.example.com&#x2F;v1beta4 offers.

To whoever wrote this, I have this unsolicited advice: being obnoxious about your competitor is very off-putting to the reader.<p>Putting down your competitor is <i>a very</i> fine art if you don&#x27;t want to come across as a douche. Done correctly it can be hilarious though. But this is just a bull in the china shop.