HashiCorp Consul 1.22 and Nomad 1.11 End of Life: October 31, 2026
HashiCorp Consul 1.22 and Nomad 1.11 reach end of life on October 31, 2026. HashiCorp prints that day itself, as a date and not as a policy: the Consul Enterprise support page lists 1.22.x with a "Planned end of support" of October 31, 2026, and the Nomad release notes page lists 1.11.x with a "Base Support End" of October 31, 2026. Both are Standard Term Support lines: Consul 1.22 shipped on October 27, 2025 and Nomad 1.11 on November 11, 2025, and each gets roughly a year. The two products ending on the same day is not a coincidence: HashiCorp moved both to a shared April and October release model in 2026, described below in its own words.
The support policy, in HashiCorp's words
Until 2026 HashiCorp supported each product line by counting releases, not by printing dates. The Consul Long Term Support page still describes that model: "All major releases of Consul Enterprise receive Standard Term Support (STS) for approximately one year", and "With STS, each major release branch is maintained until it is three (3) releases from the latest major release. For example, Consul v1.14.x is maintained until the release of Consul v1.17.0." LTS releases ran longer: "An LTS release is maintained until it is six (6) releases from the latest major release."
From the 2.0 releases onward both products print dates. The Consul Enterprise support page says: "Starting with the April 2026 (2.x.x) release, Consul Enterprise follows the IBM Support Cycle-2 (SC2) model", and "Beginning with the v2.0.0 release, HashiCorp Consul's existing semantic versioning format (X.Y.Z) changes to IBM's Version-Modification-Fix (V.M.F) model." The Nomad release notes page uses the same framing: "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." Under that model, in Consul's wording, "V: April Version milestone starts a new support lifecycle for the version. M: October Modification milestone adds new features, but does not start a new support lifecycle. F: Monthly fixes patch the existing release without adding new features."
Support Cycle-2 itself is described on the Consul page as a "2 + 1 + 3" framework: "2 years of base support. 1 year of critical extended support. 3 years of sustained support, which does not include new fixes or enhancements." Both pages add that the extended tiers are optional, paid packages for Enterprise customers. For the lines ending now, HashiCorp's tables print the same day in every column, so there is no paid extension for Consul 1.22 or Nomad 1.11.
The tables below carry the four newest lines of each product. Where HashiCorp's table prints a date, the row says so. Where it does not, the row says where our date comes from.
Consul: the four newest lines
| Version | Released | End of life | Status |
|---|---|---|---|
| Consul 2.0 | May 24, 2026 | April 30, 2028 | Supported. HashiCorp's table prints this day as the planned end of support. Paid IBM extended tiers run longer. |
| Consul 1.22 | October 27, 2025 | October 31, 2026 | This page. Ends soon; HashiCorp's table prints the day, with no extended tier. |
| Consul 1.21 (LTS) | May 6, 2025 | April 30, 2027 | Supported. HashiCorp's table prints the day and says "Consul v1.21.x is the last LTS release." |
| Consul 1.20 | October 14, 2024 | May 24, 2026 | Ended. Not in HashiCorp's table; our date is the day Consul 2.0.0 shipped, when 1.20 became three releases behind the latest under the STS rule quoted above. |
HashiCorp prints the Consul dates on a page marked as a Consul Enterprise feature. For the community edition the Consul upgrade page says only this: "For Consul community edition users, consistently operating a maintained version requires upgrading every 4 months to the latest major release." Every Consul line is on our Consul lifecycle page.
Nomad: the four newest lines
| Version | Released | End of life | Status |
|---|---|---|---|
| Nomad 2.0 | April 21, 2026 | April 30, 2028 | Supported. HashiCorp's table prints this day as the Base Support End. Paid extended tiers run longer. |
| Nomad 1.11 | November 11, 2025 | October 31, 2026 | This page. Ends soon; HashiCorp's table prints the day in all three columns, so no paid extension. |
| Nomad 1.10 (LTS) | April 9, 2025 | April 30, 2027 | Supported. HashiCorp's table prints the day and says "Nomad v1.10.x is the last LTS release." |
| Nomad 1.9 | October 10, 2024 | April 21, 2026 | Ended. Not in HashiCorp's table; our date is the day Nomad 2.0.0 shipped, the release that put 1.9 three lines behind the latest. |
Every Nomad line is on our Nomad lifecycle page.
What to do before the date
- Pick the target. Consul 2.0 and Nomad 2.0 run until April 30, 2028 on HashiCorp's tables. The LTS lines, Consul 1.21 and Nomad 1.10, run until April 30, 2027; they are a shorter runway but a smaller jump for clusters that are not ready for the 2.0 licensing changes.
- Consul: follow HashiCorp's 2.0 guide. The Upgrade Consul to v2.0.x page says: "You can only upgrade to Consul Enterprise 2.0.x from Consul Enterprise 1.21.7 or later, running an IBM Consul Enterprise license." Consul 1.22 is later than 1.21.7, so the version requirement is met, but a cluster still on a HashiCorp-issued license must complete the license migration first. The same page says Community Edition "is not affected by the Enterprise licensing prerequisite" and should follow the General Upgrade Process.
- Nomad: use the rolling or in-place process. The Upgrade Nomad page says "Nomad strives to be backward compatible for at least 2 point release" and "Nomad does not support downgrading at this time", so test the move from 1.11 to 2.0 before touching production. Read the version-specific upgrade details first: the Nomad 2.0.0 entry covers licensing log changes for IBM Passport Advantage Online, and the 2.0.4 entry deprecates unauthenticated server join ahead of Nomad 2.1.0.
- Check the Envoy and client side. Consul's upgrade page tells operators to install a compatible Envoy version for the new Consul release and restart the sidecar proxies after each client agent. Nomad clients that take longer than the heartbeat grace period to restart can have their allocations rescheduled.
- Check the rest of the stack in the same pass. Our EOL Checker and API cover the operating systems and runtimes under the cluster.
Where IBM comes in
HashiCorp's own pages describe the IBM link in two places, and this guide repeats only what they say. The Consul upgrade page: "Beginning in v1.21, Consul licensing moved from HashiCorp to IBM. IBM offers two types of Consul Enterprise licenses for self-managed clusters: Standard and Premium." The Nomad release notes page: the 2026 changes "align with IBM's enterprise software lifecycle to ensure consistent support across IBM's software portfolio." Both pages point to an IBM support document called the "IBM HashiCorp Self-Managed Product Support Lifecycle Addendum" for the full policy.
Frequently Asked Questions
When do Consul 1.22 and Nomad 1.11 reach end of life?
Both reach end of support on October 31, 2026. HashiCorp prints that day for 1.22.x in its Consul Enterprise support table and for 1.11.x in its Nomad version support table.
Is Consul 1.22 still supported?
Yes, until October 31, 2026, the planned end of support date HashiCorp prints for Consul 1.22.x. It is a Standard Term Support release, not an LTS release; HashiCorp's page says Consul v1.21.x is the last LTS release.
Is Nomad 1.11 still supported?
Yes, until October 31, 2026, the Base Support End date HashiCorp prints for Nomad 1.11.x. HashiCorp's table shows the same day for its Extended Support and Ongoing Extended Support columns, so no paid extension runs past it.
Which version should I upgrade to?
Consul 2.0 and Nomad 2.0 each carry a planned end of support of April 30, 2028, the longest runway HashiCorp prints. The LTS lines, Consul 1.21 and Nomad 1.10, both end on April 30, 2027, which is still six months later than the lines ending now.
Do these dates apply to the community editions?
HashiCorp prints the Consul table on its Consul Enterprise support page and the Nomad table on the Nomad release notes page. For Consul community edition, HashiCorp's upgrade page says that consistently operating a maintained version requires upgrading every 4 months to the latest major release, so community users should treat the newest release line as the only maintained one.
Related
- Consul 1.22 · Nomad 1.11 — the live status pages with their EOL Risk Scores
- Consul · Nomad — every line's dates
- Consul 2.0 · Nomad 2.0 — the upgrade targets
- How we verify our dates — the rules every number on this site is held to