Release v3.2.0

Registry Module version 3.2.0

Changelog

• Added compatibility with Kubernetes versions 1.30.x and 1.31.x.

NOTE: This release only extends the Kubernetes compatibility to versions 1.30 and 1.31. No functional changes are included, users can continue using their current version.

Upgrade path

To upgrade this module from v3.1.0 to v3.2.0, you need to download this new version, then apply the kustomize project. No further action is required.

Preview v3.2.0-rc.13

Registry Module version 3.2.0

Changelog

• Added compatibility with Kubernetes versions 1.30.x and 1.31.x.

Upgrade path

To upgrade this module from v3.1.0 to v3.2.0, you need to download this new version, then apply the kustomize project. No further action is required.

Preview v3.2.0-rc.7

Registry Module version 3.2.0

Changelog

• Added compatibility with Kubernetes versions 1.30.x and 1.31.x.

Upgrade path

To upgrade this module from v3.1.0 to v3.2.0, you need to download this new version, then apply the kustomize project. No further action is required.

Preview v3.2.0-rc.4

Registry Module version 3.2.0

Changelog

• Added compatibility with Kubernetes versions 1.30.x and 1.31.x.

Upgrade path

To upgrade this module from v3.1.0 to v3.2.0, you need to download this new version, then apply the kustomize project. No further action is required.

Release v3.1.0

Registry Module version 3.1.0

Changelog

• Added compatibility with Kubernetes versions 1.26.x, 1.27.x, 1.28.x and 1.29.x.

NOTE: This release only extends the Kubernetes compatibility to versions 1.26, 1.27, 1.28 and 1.29. No functional changes are included, users can continue using their current version.

Upgrade path

To upgrade this module from v3.0.2 to v3.1.0, you need to download this new version, then apply the kustomize project. No further action is required.

Preview v3.1.0-rc.6

Registry Module version 3.1.0

Changelog

• Added compatibility with Kubernetes versions 1.26.x, 1.27.x, 1.28.x and 1.29.x.

Upgrade path

To upgrade this module from v3.0.2 to v3.1.0, you need to download this new version, then apply the kustomize project. No further action is required.

Preview v3.1.0-rc.5

Registry Module version 3.1.0

Changelog

• Added compatibility with Kubernetes versions 1.26.x, 1.27.x and 1.28.x.

Upgrade path

To upgrade this module from v3.0.2 to v3.1.0, you need to download this new version, then apply the kustomize project. No further action is required.

Release v3.0.2

Registry Module version 3.0.2

Changelog

• Added compatibility with Kubernetes versions 1.24.x and 1.25.x.
• Updated Trivy cronjob with new apiversion

Upgrade path

To upgrade this module from v3.0.1 to v3.0.2, you need to download this new version, then apply the kustomize project. No further action is required.

Release v3.0.1

Registry Module version 3.0.1

Changelog

• The trivy configuration has been updated to download the new image with the updated vulnerability database every night. To do this we have added: an image that is built every night, an ad-hoc rbac and a cronjob to restart the pod. The new image is downloaded from the following repository.

Upgrade path

To upgrade this module from v3.0.0 to v3.0.1, you need to download this new version, then apply the kustomize project. No further action is required.

Release v3.0.0

Registry Module version 3.0.0

This is a major release containing an update to Harbor package with breaking changes.

Changelog

• Update Harbor from version v2.4.2 to v2.7.0.
• ⚠️ Changed the namespace from Harbor to Registry. This change was made to help when upgrading from previous versions using the approach lift and shift migration.
• ⚠️ Removed Clair as it is no longer the default scanner on Harbor since version 2.2
• The trivy configuration has been updated to download the vulnerability database once a day. To do this we have added: an init container in the statefullset, an ad-hoc rbac and a cronjob to restart the pod.
• The official exporter has been added in order to retrieve more metrics via prometheus.
• The official grafana dashboard has been added with some changes.
• An alert on Prometheus has been added to verify the actual running of the Harbor components

Upgrade path

There's no supported upgrade path for this module from v2.0.0 to v3.0.0, the default namespace has also changed from harbor to registry.

The recommended approach is a lift and shift migration. Start by copying over all the images from the old instance to the new one using Harbor's native replication and then sync the users and permissions.