|
|
|
|
|
by fesc
1059 days ago
|
|
I stopped reading when the solution for DNS was AWS and the solution for stateful sets was AWS EC2. This is just a very weird comparison. Seems like the author doesn’t understand why people run K8s. Of course they also “managed” several k8s clusters using… wait for it… AWS. 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. And if you do need nomad on AWS then that’s fine as well, but it’s not comparable to k8s in general. |
|
And if self-hosting Nomad on AWS is (allegedly) so much easier than operating managed k8s (EKS), isn't that more damning rather than less?
The all-in AWS answer I suppose would be ECS. I quite like it but I think for anything beyond small, more than a few services part of the same system, I can understand wanting to run Nomad (or use EKS) instead.