Approaching26 days from today

HashiCorp Consul 1.22 end of life

Consul 1.22 reaches end of support on 31 October 2026, according to HashiCorp's Consul Enterprise support page. It is not a long-term support release. 1.22.0 shipped on 27 October 2025. The last Community Edition build was 1.22.7 in April 2026, and Enterprise builds reached 1.22.12+ent in September 2026. Consul 1.22 is under the Business Source License.

End of life
31 October 2026
Released
Oct 2025
Final release
1.22.12+ent (Community Edition: 1.22.7)
Successor
Consul 2.0 (supported to 30 April 2028)

Date published by HashiCorp Consul Enterprise support policy. We do not publish a lifecycle date we cannot source.

Last reviewed

What actually stops on 31 October 2026

  • Enterprise fixes on the 1.22 branch. HashiCorp's table lists no IBM Extended Support or Ongoing Extended Support for 1.22.x, so 31 October 2026 is the end.
  • Community Edition builds, which stopped earlier. 1.22.7, published on 25 April 2026, is the last one. Public releases have been on 2.0 since 2.0.0 in May 2026.
  • A route back to LTS. 1.21.x is the last LTS line, supported to 30 April 2027, and a cluster on 1.22 cannot step back to it. The forward path is 2.0.

What actually breaks in the upgrade

2.0 is the only forward line

HashiCorp lists end of support for 2.0.x on 30 April 2028, with IBM Extended Support to 30 April 2029 and IBM Ongoing Extended Support to 30 April 2032. The two extended packages are optional and paid, for Enterprise customers.

Community Edition users are already behind

Enterprise builds on 1.22 continued to 1.22.12+ent on 10 September 2026. Community Edition stopped at 1.22.7 in April. A Community Edition cluster on 1.22 has had no new build for five months, so treat the upgrade to 2.0 as overdue, not as an end-of-October task.

The licence does not change

Consul moved from MPL 2.0 to the Business Source License at 1.17.0, and 1.22 and 2.0 are both under it. The last MPL 2.0 releases are 1.16.0 to 1.16.3. If the licence is the real problem, the choice is between an old MPL line and a move to another coordination store.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Upgrade to 2.0The current line, under IBM's Support Cycle-2 model.WeeksEngineering time, plus an Enterprise subscription if you use oneThe supported path, to 30 April 2028 and longer with IBM's paid extensions.
OSSeva supported upgrade and operationsOSSeva runs the upgrade to 2.0 or a migration, and operates the clusters.WeeksSubscriptionFor teams that want the move done by engineers who run Consul every day.
Migrate the workloadMove service discovery and key-value use to etcd or platform-native tooling.QuartersEngineering timeRight when the BSL terms or the IBM support model are the deciding issue.
Stay on 1.22No fixes from HashiCorp after 31 October 2026.NoneZero nowConsul's ACLs and service mesh certificate authority decide which services can talk. A poor place to carry unfixed issues.

What OSSeva does for HashiCorp Consul 1.22

OSSeva supports this line

OSSeva provides supported upgrades, migration and operations for Consul 1.22 clusters on the Assure and Operate tiers, including the move to 2.0. Consul 1.22 is under the Business Source License, so OSSeva does not redistribute modified 1.22 code. For the MPL 2.0 Consul 1.16 line (1.16.3 and earlier), OSSeva ships patched builds.

HashiCorp Consul extended support

What your auditor will say

PCI DSS v4 Requirement 6.3.3

Consul's ACL system and its service mesh certificate authority control which services can reach each other. A cluster on an unsupported line is a component without applicable security patches.

SOC 2 CC7.1

Auditors ask for evidence that production systems receive security fixes. After 31 October 2026 that evidence has to come from the upgrade to 2.0, or from a documented plan with a named supplier.

Compliance library Every HashiCorp Consul version and end-of-life date

HashiCorp Consul 1.22: common questions

When does Consul 1.22 reach end of support?

On 31 October 2026, according to HashiCorp's Consul Enterprise support page. No IBM extended support package is listed for 1.22.

Is Consul 1.22 an LTS release?

No. 1.21.x is the last LTS release and is supported until 30 April 2027. From 2.0, Consul Enterprise follows IBM's Support Cycle-2 model instead of LTS releases.

What is the last Consul 1.22 release?

1.22.7 for Community Edition, published on 25 April 2026. Enterprise builds continued to 1.22.12+ent, published on 10 September 2026.

Which Consul versions are supported after October 2026?

2.0.x, supported to 30 April 2028, and 1.21.x (LTS) until 30 April 2027. The latest 2.0 release is 2.0.4, from 10 September 2026.

Is Consul 1.22 open source?

Not under an OSI licence. Consul 1.17.0 and later are under the Business Source License 1.1. The last MPL 2.0 releases are 1.16.0 to 1.16.3.

Still running HashiCorp Consul 1.22?

Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.