EOL.WikiEOL.Wiki
← ← Back to all products

etcd

Active
MiddlewareLatest Version: 3.6.12Latest Release: Jun 1, 2026

etcd is a distributed, reliable key-value store for the most critical data of a distributed system.

Support summary

etcd currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

2

0 lts

Versions

7

Latest Version

3.6.12

Active Support

2

EOL

5

Lifecycle Timeline

Today
3.6
3.6
3.5
3.5
3.4
3.4
3.3
3.3
3.2
3.2
3.1
3.1
3.0
3.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.6May 15, 2025YesNo3.6.12No
Active
3.5Jun 15, 2021YesNo3.5.31No
Active
3.4Aug 30, 2019NoMay 15, 20253.4.45No
EOL
3.3Feb 1, 2018NoOct 15, 20213.3.27No
EOL
3.2Jun 9, 2017NoMar 28, 20213.2.32No
EOL
3.1Jan 20, 2017NoOct 10, 20183.1.20No
EOL
3.0Jun 30, 2016NoJan 20, 20173.0.17No
EOL

Data sources

Frequently Asked Questions

Which versions of etcd have reached end of life?
The following etcd versions have reached end of life and no longer receive security updates: 3.4, 3.3, 3.2, 3.1, 3.0. It is recommended to upgrade to a supported version.
Is it safe to continue using etcd 3.4?
etcd 3.4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of etcd?
The latest version of etcd is 3.6.12, released in the 3.6 release cycle.
How many versions of etcd are currently supported?
etcd currently has 2 actively supported version(s): 3.6, 3.5.
When does etcd 3.6 reach end of life?
etcd 3.6 does not have a specific end-of-life date announced yet.
What should I do when etcd reaches end of life?
When a etcd version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.