Levant enhances HashiCorp Nomad with reusable, automated, and operator-friendly deployments.
I joined HashiCorp back in April to work on the Nomad Ecosystem team having worked on designing and building solutions using HashiCorp Nomad as an orchestrator for a number of years. During that time I wrote Levant to enhance the user experience by providing a unified and consistent deployment workflow across all paths to production environments with improved feedback in CI systems.
Joining HashiCorp raised a broad question about the future of Levant, which I authored to use alongside Nomad and maintained as an independent open source project.
Levant is a tool aimed at enhancing and simplifying the process of submitting jobs to Nomad. It utilizes templating to allow operators to share job files across environments, while altering key parameters via variables stored in a number of supported formats.
Via a single deploy
command Levant will render the job template and provide real-time feedback on the status of the job and the subsequent deployment. In the event of a deployment failure, Levant will inspect each failed allocation and log debug information so the operator can quickly identify the issue.
We've discussed a number of options and I'm happy to announce that we've migrated Levant to the HashiCorp GitHub organization. The Nomad Ecosystem team will be taking up ongoing maintenance and enhancements. We're committed to keeping Levant supported and up-to-date with the latest Nomad features and contributions.
As an early example of how we hope this extra support will benefit the community, we worked with the HashiCorp education team to develop two guides on using Levant:
Thank you all for your support and belief in Levant. I'm looking forward to the next chapter for this and all our Ecosystem team projects.
If you have any questions or feedback, please feel free to reach out via Twitter, using the HashiCorp Nomad discuss forum, or by posting an issue on the Levant GitHub repository. Thanks from the entire Nomad Ecosystem team.
Learn the installation and verification workflow for any Linux distribution that does not include HashiCorp software in its package repository.
Learn how JWT-based authentication works in HashiCorp Nomad using a custom GitHub Action as an example of machine-to-machine authentication.
Managing multiple clusters of HashiCorp tools can be complicated. Target CLI eases the burden by using context profiles to easily switch between different clusters and environments.