Backport of Add NodeMaxAllocations to client configuration into release/1.10.x #25925
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 #25785 to be assessed for backporting due to the inclusion of the label backport/1.10.x.
The below text is copied from the body of the original PR.
Description
This PR introduces the concept of maximum allocations to the client via the client configuration file. This includes updates to the
nomad node status
command to add anAlloc Count
column to theAllocated Resources
section of the single node view. Ifnode_max_alloc
is defined it will be included as the denominator, otherwise we'll just report the count as a whole number.Testing & Reproduction steps
The below screenshots were generated by running a single agent dev cluster and passing it the minimal configuration in
command/agent/test-resources/client_with_max_allocs.hcl
.Single node status output when client.node_max_allocs is not set
Single node status output when client.node_max_allocs is set
Links
Github Issue #12783
Contributor Checklist
changelog entry using the
make cl
command.ensure regressions will be caught.
and job configuration, please update the Nomad website documentation to reflect this. Refer to
the website README for docs guidelines. Please also consider whether the
change requires notes within the upgrade guide.
Reviewer Checklist
backporting document.
in the majority of situations. The main exceptions are long-lived feature branches or merges where
history should be preserved.
within the public repository.
Overview of commits