Nomad Team Lead here -> You're definitely not alone, and we know it. Once you add Consul, Vault, namespaces, ACLs, mTLS, etc you have quite the infrastructure t

Nomad Team Lead here -> You're definitely not alone, and we know it. Once you add Consul, Vault, namespaces, ACLs, mTLS, etc you have quite the infrastructure to maintain. HashiCorp is making a big push to cloud to help alleviate this operational burden, but there's a lot we intend to do to make it easier to self-host as well. We're continually refining Terraform modules[1] to ease setup, although Nomad's own terraform directory is in dire need of updating. Running Consul and/or Vault with Nomad is definitely possible, but we need to do the hard work of testing and publishing best practices. Once you have Nomad up and running, staring at an empty job file is daunting as well! We're approaching that problem from 2 angles: better tools for guided job creation, and more modular job files. Templating tools already provide some job file modularization, but nothing as unified as the Helm/Charts experience. Nomad lacks any sort of central job repository as well. You can expect us to chip away at these problems like we've approached everything else: incremental improvements while maintaining backward compatibility. And for those willing (or eager!) to let someone else handle the operational burden for you: stay tuned for exciting things coming from HashiCorp Cloud Platform! [1] https://registry.terraform.io/modules/hashicorp/nomad/aws/latest/submodules/nomad-cluster https://registry.terraform.io/modules/hashicorp/nomad/aws/la...