Skip to content

Releases: goharbor/harbor-helm

v1.13.2

04 Feb 02:44
d4f278e
Compare
Choose a tag to compare

Harbor OSS version: v2.9.2

v1.14.0

02 Jan 08:59
7f748f8
Compare
Choose a tag to compare

Harbor OSS version: v2.10.0

Known issue

Please use helm version >= 3.10.0, when deploying harbor-helm v1.14.0 and onwards.
Issue tracking: #1671

v1.11.4

06 Dec 06:21
97e4337
Compare
Choose a tag to compare

Harbor OSS version: v2.7.4

v1.13.1

03 Nov 02:04
aa2569d
Compare
Choose a tag to compare

Harbor OSS version: v2.9.1

v1.11.3

15 Sep 02:10
3580c14
Compare
Choose a tag to compare

Harbor OSS version: v2.7.3

v1.13.0

04 Sep 09:55
fd3a4b7
Compare
Choose a tag to compare

Harbor OSS version: v2.9.0

v1.12.4

16 Aug 14:06
2f27b96
Compare
Choose a tag to compare

Harbor OSS version: v2.8.4

v1.12.3

28 Jul 10:59
a0885f4
Compare
Choose a tag to compare

Harbor OSS version: v2.8.3

v1.3.19

06 Jun 06:59
a13d6eb
Compare
Choose a tag to compare

Harbor OSS version: v1.10.18

v1.12.2

06 Jun 10:24
1e306c2
Compare
Choose a tag to compare

Harbor OSS version: v2.8.2

Known issue

  • In version v2.8.0-v2.8.2, please refrain from using the EXTERNAL REDIS USERNAME (ACL AUTH) due to issue-18892. So if you care about the registry performance, please follow the FAQ guidance to set up your Redis server that allow you to bypass this limitation, otherwise you could just ignore it.