Nomad 2.1.x release notes
Nomad version support
Beginning in April 2026, HashiCorp's self-managed products adopt new version, release, and support models. Nomad continues to target Spring and Fall feature releases, with monthly updates as needed. These changes align with IBM's enterprise software lifecycle to ensure consistent support across IBM's software portfolio.
| Version | Base Support End | Extended Support End | Ongoing Extended Support End |
|---|---|---|---|
| 1.8.x.(LTS) | April 30, 2026 | April 30, 2026 | April 30, 2026 |
| 1.10.x (LTS) | April 30, 2027 | April 30, 2027 | April 30, 2027 |
| 1.11.x | October 31, 2026 | October 31, 2026 | October 31, 2026 |
| 2.0.x | April 30, 2028 | April 30, 2029 | April 30, 2032 |
Note that Extended Support and Ongoing Extended Support are optional, paid support packages available to Enterprise customers.
Beginning with the 2.0.0 release, HashiCorp Nomad's existing semantic versioning format (X.Y.Z) moves to IBM's Version-Modification-Fix (V.M.F) model. This mapping helps make lifecycle timing clear and consistent across products.
- April ("V" milestone): Starts a new support lifecycle for the version.
- October ("M" milestone): Adds new features but does not start a new support lifecycle.
- Monthly ("F" fixes): Patch release.
Refer to the following for additional details:
- IBM HashiCorp Self-Managed Product Support Lifecycle Addendum
- Changes to HashiCorp Self-Managed Enterprise Product Release Cadence and Support
- HashiCorp Long-Term Support (LTS) releases for products released prior to March 2025. Nomad v1.10.x is the last LTS release.
- IBM Software Support Lifecycle Policies
2.1.0
Release Date: 27 October 2026
Release highlights
Nomad 2.1.0 includes the following features and improvements.
Batch job queue
You can configure an experimental batch job queue on a node pool with the
batch_queue
block. The queue holds the batch jobs that you register in the node pool and
sends them to the scheduler one at a time. The queue waits for Nomad to place
each job before it sends the next one.
A first in, first out (FIFO) queue schedules jobs in the order that you register them. A dynamic priority queue recalculates each job's priority from the job's age, the job's resource size, and how much of the node pool's resources each tenant uses. You identify tenants by namespace or by a metadata key.
Use the nomad queue commands to view the jobs in
a queue and the status of a dynamic priority queue. Refer to Batch job
queue to learn how the queue
orders jobs, and Queue batch jobs to
configure one.
Optional object type attributes in input variables
Job specification input variables support the optional() modifier in
object type constraints. When you omit an optional attribute, Nomad fills it
with the default value that you declare in optional() instead of returning
an error. Refer to Optional object type
attributes
for details.
New nomad operator snapshot filter command
The nomad operator snapshot filter command removes selected entries from an
existing snapshot file and writes the result to a copy. Use it to remove
objects from a snapshot before you restore it to a cluster, or to remove a
large number of pending evaluations when you recover a cluster from an outage.
Refer to the nomad operator snapshot filter command
reference for details.
TLS verification uses the Go standard library
Nomad now uses the Go standard library to verify TLS certificates during agent-to-agent connections. The error messages for TLS handshake failures might differ from earlier versions, so update any log alerts or scripts that match on those messages.
Breaking changes
Review the following changes before you upgrade to Nomad 2.1.0.
Server join requires the agent:write permission
When ACLs are enabled, the nomad server join command and the Join
Agent API require a token with the
agent:write permission.
Removed deprecated server join configurations
We removed the deprecated server configuration parameters retry_join,
retry_interval, retry_max, and start_join from the server block. A
server agent that still sets these parameters fails to start. Set them in the
server_join block instead.
Deprecations
Nomad 2.1.0 deprecates or removes support for the following.
Deprecated resource fields on the Allocation API
The Resources and TaskResources fields on the Go API's Allocation struct
are deprecated. Nomad servers do not populate these fields. Use the
AllocatedResources field instead.
The HTTP API no longer returns the Resources, SharedResources, and
TaskResources fields in allocation responses. Read an allocation's resources
from the AllocatedResources field instead.
Client state databases older than Nomad 0.9 are not supported
Nomad clients do not support state databases from Nomad versions older than 0.9. When you restore a client state database from a backup older than Nomad 0.9, the client fails to start.
Refer to the Nomad 2.1.0 upgrade-specific documentation for details.
Changelog
Review improvements, security fixes, and breaking changes in the changelog.