| Ah, I've submitted this as soon as I saw the notification of the new release on Github, maybe the blog post was indeed more relevant. Congratulations on this milestone release, we're using Nomad since March this year on a single 'bare-metal' server and it serves our needs perfectly. We set it up with a simple gorilla/mux API in front and use the Nomad API to submit jobs from all our other applications and it works flawlessly. With regards to 1.0's features: HCL2 is a welcome addition for us since we had a lot of repetition in our job files using artifacts for tasks. Also the addition of the PostStop lifecycle couldn't come at a better time, we were discussing workarounds for this recently. One area of potential improvement would be the behaviour of file/directory permissions through different task drivers, I know this is totally dependent of the different drivers we can use with Nomad but more than once we bumped into this while setting up our jobs (and others too [1][2]) [1] https://github.com/hashicorp/nomad/issues/2625
[2] https://github.com/hashicorp/nomad/issues/8892 Thanks for all the work your team did. I am a big fan of the Hashicorp ecosystem. |
Thanks for mentioning these. Everyone interested should definitely +1 them as we do use reaction emoji during prioritization.
The task driver dependent nature does make this tricky, but since the Nomad agent is usually run as root and controls the allocation/task directory tree we should have some options here.