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

VMware Harbor Registry

EOL
Cloud & Platforms Latest Version: 2.10.2 Latest Release: Apr 18, 2024

VMware Harbor Registry is an enterprise container registry for managing and distributing container images.

Versions

13

Latest Version

2.10.2

Active Support

0

EOL

13

Lifecycle Timeline

Today
2.10
2.10
2.9
2.9
2.8
2.8
2.7
2.7
2.6
2.6
2.5
2.5
2.4
2.4
2.3
2.3
2.2
2.2
2.1
2.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2.10Jan 17, 2024-Jan 31, 20252.10.2No
EOL
2.9Sep 15, 2023-Sep 30, 20242.9.1No
EOL
2.8May 22, 2023-May 31, 20242.8.4No
EOL
2.7Jan 5, 2023-Jan 31, 20242.7.4No
EOL
2.6Sep 1, 2022-Jun 30, 20232.6.4No
EOL
2.5Apr 26, 2022-Jun 23, 20232.5.5No
EOL
2.4Nov 3, 2021-Nov 30, 20222.4.3No
EOL
2.3Aug 16, 2021-Dec 31, 20222.3.5No
EOL
2.2Apr 19, 2021-Apr 30, 20222.2.3No
EOL
2.1Oct 23, 2020-Jul 19, 20222.1.6No
EOL
2.0Jul 9, 2020-Mar 20, 20222.0.6No
EOL
1.10Dec 19, 2019-Jun 11, 20211.10.3No
EOL
1.9Nov 18, 2019-Jan 8, 20211.9.4No
EOL

Frequently Asked Questions

Which versions of VMware Harbor Registry have reached end of life?
The following VMware Harbor Registry versions have reached end of life and no longer receive security updates: 2.10, 2.9, 2.8, 2.7, 2.6, 2.5, 2.4, 2.3 (and 5 more). It is recommended to upgrade to a supported version.
Is it safe to continue using VMware Harbor Registry 2.10?
VMware Harbor Registry 2.10 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 VMware Harbor Registry?
The latest version of VMware Harbor Registry is 2.10.2, released in the 2.10 release cycle.
What should I do when VMware Harbor Registry reaches end of life?
When a VMware Harbor Registry 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.