hashicorp / hashicorp/nomad-pack
Nomad Pack: Plan/Run benefits
- Dominant language
- Go
- Stars
- 447
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I'm new to nomad-pack but have extensive experience with Helm/kubernetes.
I can already see the benefits of `nomad-pack` as a template engine, but I'm wondering about the benefits of `nomad-pack` as a deployment tool.
Same as helm, I can use `nomad-pack render` to render templates and then use `nomad plan` and `nomad run` to run my jobs.
What are the benefits of pack plan/run? What do I lose if I use `nomad-pack` just to render jobs?
Contributor guide
Research direction
Start with the nomad-pack render, plan, and run commands, then compare them with nomad plan and nomad run as described in the issue. Document the benefits and tradeoffs of using pack for deployment versus rendering jobs only, including what users lose with the latter approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100