Runtime
HashiCorp
HashiCorp Consul 1.22, a standard (non-LTS) release, reaches end of life on 31 October 2026 — after which the 1.22 series receives no further maintenance or security releases
departs 31 Oct 2026
Quick answers
- Is it true that HashiCorp Consul 1.22 reaches end of life on 31 October 2026 — a standard release that EOLs before the 1.21 LTS?
- Yes. HashiCorp has officially announced it, effective 31 Oct 2026. Consul 1.22 is a standard, non-LTS release: it shipped on 27 October 2025 and its maintenance window ends on 31 October 2026, about a year later.
- When does it take effect?
- 31 Oct 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Move off Consul 1.22 to a release with a longer support window before 31 October 2026.
What this means for you
Consul 1.22 is a standard, non-LTS release: it shipped on 27 October 2025 and its maintenance window ends on 31 October 2026, about a year later. After that date the 1.22 line gets no further releases, including security patches. The counter-intuitive part is the version ordering: 1.22 goes end-of-life *before* the older 1.21, because 1.21 is a designated LTS release supported through 30 April 2027 while 1.22 is a standard release with a shorter window. A higher version number does not mean a longer runway here. Anyone running `hashicorp/consul:1.22` (or the legacy `consul:1.22` image) in a service mesh, KV store, or service-discovery layer is on a build that stops receiving security fixes at the end of October 2026 — and for infrastructure that sits in the middle of service-to-service traffic, an unpatched Consul is a meaningful exposure.
Where to go
Move off Consul 1.22 to a release with a longer support window before 31 October 2026. Per endoflife.date, the two supported landing spots are the **1.21 LTS** line (supported through 30 April 2027) and the newest major, **Consul 2.0** (supported through 30 April 2028). In Dockerfiles, Helm charts, and Nomad/Kubernetes manifests, replace `hashicorp/consul:1.22` tags with a supported release, and rehearse the upgrade on a non-production cluster first — Consul upgrades are version-sequenced and agents must be upgraded in a supported order (servers before clients, one minor at a time where required), so read the upstream upgrade guide for your target version before touching production. If you need a specific version pinned for a service mesh with sidecars, verify Envoy compatibility for the target Consul version as part of the rehearsal.
- Consul 1.21 (LTS) — supported through 30 April 2027, the extended-support landing spot
- Consul 2.0 — the newest major line, supported through 30 April 2028
HashiCorp Consul 1.22 reaches end of life on 31 October 2026. It shipped on 27 October 2025 as a standard release, and roughly a year later its maintenance window closes — after which the 1.22 series gets no further releases, security patches included.
The version numbers are misleading
The trap here is that 1.22 goes end-of-life before 1.21. That looks backwards until you notice the release types: Consul 1.21 is a designated LTS release, supported through 30 April 2027, while 1.22 is a standard release with a shorter, roughly one-year window. A newer version number is not a promise of a longer runway. If you upgraded to 1.22 assuming “latest is safest,” you are actually on a build that expires sooner than the LTS you skipped.
Who this affects
Anyone running Consul 1.22 as their service mesh, KV store, or service-discovery layer — via the hashicorp/consul:1.22 container image (or the legacy consul:1.22 official image), a Helm chart, or a Nomad/Kubernetes deployment. Consul sits in the middle of service-to-service traffic and configuration, so an unpatched control plane is not a low-stakes dependency to leave behind.
What to do
Move to a release with a longer support window before 31 October 2026. endoflife.date lists two supported targets: the 1.21 LTS (through 30 April 2027) and the newest major, Consul 2.0 (through 30 April 2028). Replace hashicorp/consul:1.22 tags in your images and manifests with a supported version, and rehearse on a non-production cluster first — Consul upgrades are version-sequenced (upgrade servers before clients, and step through minors in the order upstream requires), so follow the official upgrade guide for your chosen target. For a service mesh, confirm Envoy compatibility for the target Consul version as part of the rehearsal.
Entry changelog
- — last reviewed.
- — Entry created from the HashiCorp Consul support lifecycle on endoflife.date, verified against its JSON API (endoflife.date/api/consul.json): cycle 1.22, eol 2026-10-31, lts false, latest 1.22.7 — and cycle 1.21 marked lts true with eol 2027-04-30, which is the basis for the "standard release EOLs before the LTS" framing. Dates quoted, not inferred. Detectable via the current `hashicorp/consul` image tag and the legacy `consul` official image, both at the 1.22 tag; fingerprints CLI-validated against surviving sibling tags to avoid boundary collisions.
Put this countdown in your README
Building on HashiCorp? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/consul-1-22-end-of-life)Spot an error or a changed date? Tell us and it’s corrected the same night.