Recent articles
Harbor v2.11 release - The SBOMs release
Bonjour Harbor KubeCon + CloudNativeCon Europe 2024 - Paris
Harbor v2.10 release
Harbor Recap from KubeCon Chicago 2023
Harbor v2.11 release - The SBOMs release
June 6, 2024
Orlin Vasilev
The Harbor team is thrilled to announce the release of Harbor 2.11! Packed with groundbreaking features, performance enhancements, and new integrations, this release sets a new standard for container registry management. Let’s dive into what’s new and why you should be as excited as we are!
Happy 10th birthday Kubernetes
Harbor 2.11 introduces robust support for generating Software Bill of Materials (SBOM) either manually or automatically. This powerful feature enhances transparency and security by allowing users to view, download, and replicate SBOMs across different instances of Harbor.
For those handling massive concurrent pushes to a project, enabling the Automatically generate SBOM on push
feature ensures smooth operation. Simply set core.quotaUpdateProvider: redis
in values.yaml
for Harbor-helm or core.quota_update_provider: redis
in harbor.yml
for Docker-compose installations. This tweak reduces overall resource consumption, optimizing database connections, CPU usage, and memory.
Read more
In this release, Harbor proudly supports OCI Distribution Spec v1.1.0. This update ensures that Harbor stays at the forefront of container image distribution, providing users with the latest standards and functionalities for seamless container management. Read more
One of the standout features in Harbor 2.11 is the seamless integration with VolcEngine Registry. Users can now effortlessly replicate images to and from the VolcEngine registry. This integration enhances interoperability and flexibility, allowing for a more versatile and dynamic Harbor ecosystem.
In our commitment to inclusivity and accessibility, Harbor 2.11 introduces a Korean language translation for the user interface. This update ensures that Korean-speaking users can navigate and utilize Harbor more efficiently, making the platform more user-friendly and globally accessible.
Performance improvements are always a priority. In Harbor 2.11, a significant enhancement is the ability to skip transactions for POST /service/token requests. Contributed by @liubin in #19339, this update streamlines token service operations, enhancing overall performance.
Thanks to @tostt in #19915, Harbor’s internationalization has been further refined with updates to the French (fr-fr) translations. This continuous improvement ensures that non-English speaking users have a smooth and coherent experience.
It’s worth noting a known issue affecting versions v2.10.x and v2.9.x. When performing pull-based replication from a GitLab registry to Harbor, users must be members of the source project in GitLab, even if it’s a public project. This membership requirement is essential to perform the replication successfully.
Harbor 2.11 is a testament to our commitment to delivering cutting-edge features and enhancements to our users. From advanced SBOM management and OCI spec support to seamless VolcEngine integration and new language translations, this release has something for everyone. Upgrade today and experience the future of container registry management with Harbor 2.11!
Stay tuned for more updates and happy containerizing! ๐
AllForNothing alrs an-toine blueswen dependabot eltociear hasonhai Iceber jm-nab liubin LiuShuaiyi majorteach microyahoo MinerYang prima101112 ShengqiWang stonezdj testwill tkatkov tostt tpoxa twhiteman wy65701436 xuelichao YangJiao0817 zyyw
This release wouldn’t have been possible without the dedication and support of our growing community of contributors. Your efforts are invaluable!
For a detailed list of changes and updates, dive into the full release notes here.
Upgrade to Harbor 2.11 today and experience the latest enhancements firsthand!
Get updates on X(Twitter):
@project_harbor
Chat with us on Slack:
#harbor
and
#harbor-dev
on the
CNCF Slack
Collaborate with us on
GitHub
Attend the
community meetings
ย ย
Orlin Vasilev
Harbor Community/DevRel Lead
GitHub:
@OrlinVasilev
X(Twitter):
@OrlinVasilev