3 ms·
I've worked on a fargate + lambda migration to Nomad. At this point I definitely would have preferred to have gone with k8s. Nomad is still relatively complex,
by twunde 4y ago
I've worked on a fargate + lambda migration to Nomad. At this point I definitely would have preferred to have gone with k8s. Nomad is still relatively complex, to the point where K8s is only somewhat more complex but made up with a bigger community and more tooling and features.
Features I miss:
- ephemeral containers
- dns integration with cloud providers
- Up to date tutorials/examples, especially complex examples
- Better out of the box validation/linting
- sofixa 4y agoDisclaimer: I work at Hashicorp, not on Nomad (but I've been a fan long before joining) opinions my own, etc. > dns integration with cloud providers You have that, with an intermediary in the form of Consul Terraform Sync (runs Terraform based on events in Consul like new service or node - so you can have a terraform module doing your DNS integration, another opening firewalls, etc. all run after a service has been added/updated). > Better out of the box validation/linting How so? Both do fine client side validation/linting out of the box. Ephemeral containers would be really cool to have.