Release Notes for VMware Harbor Registry Integration with Enterprise PKS

v1.8.1

Release Date: July 9, 2019

VMware Harbor Registry v1.8.1 is a general availability release with several new features and fixes.

Supported upgrade paths:

  • From Harbor v1.7.x to Harbor v1.8.1
  • From Harbor v1.6.x to Harbor v1.8.1

New features:

  • Support for OpenID Connect
  • Robot accounts
  • Replication advancements
  • Health Check API
  • Support for defining cron-based scheduled tasks
  • API explorer integration
  • Introduce a new master role to project
  • Introduce harbor.yml as the replacement of harbor.cfg and refactor the prepare script
  • Enhancement of the Job Service engine to include webhook events
  • Docker Registry upgraded to v2.7.1
  • Remove adminserver container

For additional details, refer to the Harbor v1.8.0 release at the Harbor GitHub repository.

Fixed issues:

  • Cron job (template) will be lost after migrating to latest version 1.8.0 from other versions (1.6.x/1.7.x) area/job-services kind/bug target/1.8.1.
  • Pull based replication not support library/hipache in docker hub area/replication target/1.8.1.
  • Pull based replication not support library/redis:2.8 in docker hub area/replication target/1.8.1.
  • Swagger API version of 1.8.0 target/1.8.1.
  • http_auth always onboard configuration doesn’t work as expected target/1.8.1.

Known issues:

  • After upgrade from v1.6.x, the scheduled setting of “Scan All” is reset to “None” and the administrator will need to update the schedule again.
  • The label filter in replication policies will be lost after upgrade (#7762).
  • When the internal redis is down, the health check API may return a 502 Bad Gateway error (#7691).
  • The Harbor API does not support pulling or pushing the manifest list from Docker registry. When replicating the manifest list, the image whose architecture is amd64 and OS is linux (if found) or the first one will be replicated (#6522).
  • Harbor Tile UAA authentication does not support UAA with SAML backend.

Support matrix:

  • Enterprise PKS v1.4.x, v1.5.x
  • Ops Manager v2.4, v2.5, v2.6 (refer to the Enterprise PKS release notes for specific matching versions)

v1.7.5

Release Date: May 2, 2019

VMware Harbor Registry v1.7.5 is a minor release.

Supported upgrade paths:

  • From Harbor v1.7.4 to Harbor v1.7.5
  • From Harbor v1.7.3 to Harbor v1.7.5
  • From Harbor v1.7.2 to Harbor v1.7.5
  • From Harbor v1.6 to Harbor v1.7.5
  • From Harbor v1.5 to Harbor v1.7.5

Fixed issues:

  • Harbor upgrade from 1.7.2 to 1.7.4 failed with error “Failed to update database, error: pq: must be owner of relation schema_migrations”
  • Bumped up Clair to v2.0.8
  • Fixed issues in supporting Windows images.
  • Removed user-agent check-in notification handler.
  • Fixed the issue global search not working if chartmusuem is not installed.

Known issues:

Support matrix:

  • Supports PKS v1.3.x, 1.4.x
  • Supports Ops Manager v2.3, Ops Manager v2.4

v1.7.4

Release Date: March 26, 2019

VMware Harbor Registry v1.7.4 is a minor release.

Supported upgrade paths:

  • From Harbor v1.7.3 to Harbor v1.7.4
  • From Harbor v1.7.2 to Harbor v1.7.4
  • From Harbor v1.6 to Harbor v1.7.4
  • From Harbor v1.5 to Harbor v1.7.4

Fixed issues:

  • Not able to increase the disk size of the harbor VM.
  • notary-server and notary-signer cannot start after upgrading to 1.7.4
  • Other Harbor issues listed at the Harbor repository in GitHub.

v1.7.3

Release Date: February 20, 2019

VMware Harbor Registry v1.7.3 is a minor release.

Supported upgrade paths:

  • From Harbor v1.7.2 to Harbor v1.7.3
  • From Harbor v1.7.1 to Harbor v1.7.3
  • From Harbor v1.6 to Harbor v1.7.3
  • From Harbor v1.5 to Harbor v1.7.3

Fixed issues:

v1.7.2

Release Date: February 5, 2019

VMware Harbor Registry v1.7.2 is a minor release.

Supported upgrade paths:

  • From Harbor v1.6 to Harbor v1.7.2
  • From Harbor v1.5 to Harbor v1.7.2

Fixed issues:

  • The Harbor upgrade from 1.6.0 to 1.7.1 known issue.
  • Ctl start failed issue when NFS storage is configured.

v1.7.1

Release Date: January 16, 2019

WARNING: We recommend that you skip the Harbor v1.7.1 release and install or upgrade to Harbor v1.7.2.

VMware Harbor Registry v1.7.1 is a general availability release with several new features and fixes.

New features:

Fixed issues:

  • You can now change the Harbor admin password using the Harbor web interface. You must enter the new password in the Admin Password to run smoke test field of the Credentials pane in the Harbor tile before reinstalling or upgrading the Harbor tile.
  • The parameter registry is added by default and does not have to be added manually to the no_proxy field for Clair proxy configuration.

Known issues:

When upgrading from Harbor v1.6.0 to v1.7.1, the upgrade procedure may fail with the following error message: 1 of 3 pre-start scripts failed. Failed Jobs: harbor. The workaround is to log in to the Harbor VM with BOSH and check the Docker images. If there are any Docker images found for vmware/harbor-log, remove the images before migration. After removing the images, click Apply Changes in Ops Manager and retry the upgrade. This issue is addressed in Harbor v1.7.2.

For guidance on logging in to the Harbor VM using BOSH, see Managing PKS Deployments with BOSH.

See the following example commands to check for Docker images in vmare/harbor-log:

alias docker='/var/vcap/packages/docker/bin/docker -H unix:///var/vcap/sys/run/docker/dockerd.sock'
docker images | grep vmware/harbor-log

See the following example command to remove any Docker images found for vmware/harbor-log:

docker rmi IMAGES-ID-OF-VMWARE/HARBOR-LOG

v1.6.3

Release Date: December 21, 2018

The Harbor 1.6.3 tile is a maintenance release.

Fixed issues:

  • Fixed issue with Clair’s inability to scan S3 storage if it does not have the proper CA certificate for the S3 storage URL.
  • Fixed issue with user being unable to sign images using Notary after upgrading to v1.6.

v1.6.0

Release Date: Sept 27, 2018

For more information about new Harbor features, see the release notes for Harbor v1.6.0 in the Harbor GitHub repository.

New features:

  • Support for customizing Docker container network address pool in the Harbor tile configuration.
  • Disables Clair update by default in the Harbor tile.

Fixed issues:

  • Email/UAA Settings tab in the Harbor UI is reset to defaults after a resurrection event occurs in BOSH.
  • When using S3 storage in Harbor tile to point to an internal S3 object store, Harbor does not trust the issuer.

Known issues:

  • If you change the Harbor admin password using the Harbor web interface, subsequent attempts to use Apply Changesin Ops Manager to update the Harbor tile will fail. To avoid this issue, do not change the Harbor password using the Harbor web interface.

v1.5.2

NOTE: This release is not supported as of 4/10/2019.

Release Date: July 23, 2018

Minor release to fix issues in v1.5.x.

Fixed issues:

  • Continuous traffic towards security-tracker.debian.org from Clair.
  • Harbor upgrade from v1.4.2 to v1.5.1 failing.
  • Email settings tab in Harbor UI is reset to defaults after a resurrection.

v1.5.1

NOTE: This release is not supported as of 4/10/2019.

Release Date: June 28, 2018

General Availability release to be used with PKS v1.1.x and Pivotal Application Service (PAS) v2.1.x.

New features:

  • Harbor Tile v1.5.1 includes the Harbor v1.5.1 GA release build.
  • Harbor Tile v1.5.1 is fully compatible with PKS v1.1.0 (but not PKS v1.0.x).

v1.4.2

NOTE: This release is not supported as of 4/10/2019.

Release Date: May 21, 2018

General Availability release to be used with Enterprise PKS v1.x and PAS v2.x.

New features:

  • Allow configuring the HTTP proxy for Clair in the Harbor Tile.
  • Allow configuring v4auth and secure for S3-compatible registry storage in the Harbor Tile.
  • Support GCS as the docker registry storage in the Harbor Tile.
  • Support upgrade from Harbor Tile v1.4.1 to v1.4.2.
  • Encryption: No changes to encryption with this release.

Fixed issues:

  • Harbor Tile status shows failure after Harbor VM is rebooted manually or by vSphere HA.
  • Harbor service sometimes cannot start after clicking Apply changes in Ops Manager.
  • Clair or Notary cannot be turned off in Harbor Tile.
  • Enterprise PKS UAA user with admin rights does not have privilege.

v1.4.1

NOTE: This release is not supported as of 4/10/2019.

Release Date: February 8, 2018

Fixed issues:

  • #4244 Harbor Tile deployment fails when the network name in BOSH Director contains upper-case characters.

Known issues:

  • #4214 Deleting multiple tags that point to the same image may return a 500 error.
  • #4217 When using UAA, cannot onboard users with the same email address. Email addresses must be unique.
  • Users may experience unexpected behavior with some versions of the Firefox browser when accessing the Harbor UI. Suggest use of Google Chrome for best results.
  • Harbor uses default internal networks (default Docker IPs) that may overlap with customer production networks and cause issues, such as preventing communication with the registry from outside of the VM. For more information, see PKS is unable to access the Harbor web interface in the Pivotal Support Knowledge Base.

v1.4.0

NOTE: This release is not supported as of 4/10/2019.

Release Date: February 7, 2018

New features:

  • User Account and Authentication (UAA) integration capability with PAS and Enterprise PKS.
  • External S3 storage capability.
  • Replication policy rework to support wildcard, scheduled replication.
  • Support for repository-level description.
  • Batch operation on projects/repositories/users from UI.

Known issues:

  • #4214 Deleting multiple tags that point to the same image may return a 500 error.
  • #4217 When using UAA, cannot onboard users with the same email address. Email addresses must be unique.
  • Users may experience unexpected behaviour with some versions of the Firefox browser when accessing the Harbor UI. Suggest use of Google Chrome for best results.

v1.3.1

NOTE: This release is not supported as of 4/10/2019.

Release Date: January 16, 2018

Fixed issues:

  • Fixed: #3942 Enterprise PKS/Harbor: Harbor services cannot start after Harbor VM is rebooted.
  • Fixed: #3849 Failed to stop dockerd service when updating the Harbor tile.
  • Fixed: #3823 Harbor tile should support user-provided certificate signed with other than Ops Manager root CA.
  • Fixed: #3814 Add Verify LDAP Certificate option in Harbor Tile UI.

v1.3.0

Release Date: December 21, 2017

New features:

  • Initial release of the VMware Harbor Registry.
  • Adds a Harbor tile to Ops Manager.
Create a pull request or raise an issue on the source for this page in GitHub