EOL.Wiki EOL.Wiki
← ← Back to all products

Longhorn

Active
Other Latest Version: 1.12.0 Latest Release: Jun 2, 2026

Versions

12

Latest Version

1.12.0

Active Support

5

EOL

7

Lifecycle Timeline

Today
1.12
1.12
1.11
1.11
1.10
1.10
1.9
1.9
1.8
1.8
1.7
1.7
1.6
1.6
1.5
1.5
1.4
1.4
1.3
1.3
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.12Jun 2, 2026YesDec 2, 20271.12.0No
Active
1.11Jan 29, 2026YesJul 29, 20271.11.2No
Active
1.10Sep 25, 2025YesMar 25, 20271.10.2No
Active
1.9May 27, 2025YesNov 27, 20261.9.2No
Active
1.8Jan 22, 2025YesJul 22, 20261.8.2No
Active
1.7Aug 20, 2024NoSep 4, 20251.7.3No
EOL
1.6Feb 1, 2024NoMar 29, 20251.6.4No
EOL
1.5Jul 7, 2023NoJul 19, 20241.5.5No
EOL
1.4Dec 30, 2022NoMar 13, 20241.4.4No
EOL
1.3Jun 15, 2022NoAug 11, 20231.3.3No
EOL
1.2Aug 31, 2021NoOct 6, 20221.2.6No
EOL
1.1Dec 18, 2020NoApr 23, 20221.1.3No
EOL

Frequently Asked Questions

Which versions of Longhorn have reached end of life?
The following Longhorn versions have reached end of life and no longer receive security updates: 1.7, 1.6, 1.5, 1.4, 1.3, 1.2, 1.1. It is recommended to upgrade to a supported version.
Is it safe to continue using Longhorn 1.7?
Longhorn 1.7 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 Longhorn?
The latest version of Longhorn is 1.12.0, released in the 1.12 release cycle.
How many versions of Longhorn are currently supported?
Longhorn currently has 5 actively supported version(s): 1.12, 1.11, 1.10, 1.9, 1.8.
When does Longhorn 1.12 reach end of life?
Longhorn 1.12 is scheduled to reach end of life on Dec 2, 2027.
What should I do when Longhorn reaches end of life?
When a Longhorn 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.