This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Backport of Nomad runner install CPU and memory flags into release/0.11.x #4801
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #4798 to be assessed for backporting due to the inclusion of the label backport/0.11.x.
The below text is copied from the body of the original PR.
The Nomad runner install configuration has fields for CPU and memory, but no flags for the user to set them - this PR adds those flags. This fix stems from a discussion on HashiCorp Discuss, where a user installing a runner had insufficient resources on their Nomad client to run the runner, and I realized I could not suggest setting lower memory or CPU on the runner because there were no CLI flags to support it.
Overview of commits