This topic describes how to use Harbor's replication feature to push images from Harbor to CR for unified image management and distribution. This topic applies to both Harbor 2.11 and later and versions earlier than Harbor 2.11. The configuration differs only slightly in the step for adding the destination registry.

Scenario introduction

Push the Nginx image in the Harbor project harborporject to a CR instance. The configuration differs slightly by Harbor version. The details are as follows.

Item	Harbor 2.11 and later	Harbor versions earlier than 2.11
Provider type	Select VolcEngine CR as the provider.	Select Docker Registry as the provider.
Authentication method	Use the Volcano Engine root user's AK/SK for authentication.	Use the CR instance's username and password for authentication.
Destination namespace	If the destination namespace is left unspecified, a namespace with the same name will be created in CR during synchronization.	The corresponding namespace must be created in CR in advance.

Prerequisites

A project (harborproject) has been created in Harbor, and the images to be replicated have been pushed to the project.

For information about how to create a project, see Create Projects.

For information about how to push images, see Pulling and Pushing Images in the Docker Client.

For information about how to create a CR instance, see Creating Standard Edition instances.

Access credentials for logging in to the CR instance have been obtained.

For Harbor 2.11 and later, you need to obtain the account AK/SK. For more information, see API Access Key Management.

For Harbor versions earlier than 2.11, you need to obtain the username and password to log in to the CR instance. For details about how to obtain them, see Standard Edition instance access credentials.

The destination namespace has been created.

For Harbor versions earlier than 2.11, you need to create the corresponding namespace in CR in advance. For detailed instructions, see Creating namespaces.

Limits

The namespace name in CR must be 2 to 90 characters in length. If a Harbor project name is 1 character long, manually set a namespace name with at least 2 characters under the rule's "Destination > Namespace".

Procedure

Step 1: Add a destination registry

Log in to the Harbor console.

In the left navigation pane, click Administration > Registries.

On the Registries page, click New Endpoint to create a destination registry.

Harbor 2.11 and later

Harbor versions earlier than 2.11

tip

This topic describes only the parameters required for this procedure. For other parameters, keep the default settings.

After configuration is complete, click Test Connection to verify connectivity to the destination instance.

Parameter	Description
Provider	Select VolcEngine CR.
Name	Enter a custom name for the destination registry.
Endpoint URL	Enter the domain name of the destination CR instance. You can find the domain name under Access domain name on the Overview page of the instance. When filling in this parameter, add https:// before the access domain name. The correct format is https://****-cn-beijing.cr.volces.com.
Access ID	Enter the account Access Key ID and Secret Access Key. For more information, see API Access Key Management.
Access Secret

Click Confirm to complete the operation.

Step 2: Configure Harbor image replication

Log in to the Harbor console.

In the left navigation pane, click Administration > Replications.

On the Replications page, click New Replication Rule to create an image replication rule.

Parameter	Description
Name	Enter a custom replication rule name. In this example, enter harbor2cr.
Replication mode	Select Push-based.
Name	Enter the name pattern of resources to replicate. In this topic, to replicate all images under harborproject, enter harborproject/**.
Destination Registry	Select the destination CR instance added in Step 1.
Destination	Enter the name of the namespace created in CR. This topic uses crnamespace as an example. The namespace name in CR must be 2 to 90 characters in length. If a Harbor project name is only 1 character long, configure a namespace name that is at least 2 characters long.

Click Save to complete the operation.

Step 3: Start Harbor image replication

On the Replications page, select the target replication rule harbor2cr and click Replicate.

On the confirmation page, click Replicate.

In the Tasks section at the bottom of the page, view the status of the target task. If the status is Succeed, the replication task has succeeded.

Validate results

Check whether the image has been replicated to the destination instance and namespace in CR. In this example, the crnamespace namespace of the destination instance ****-test already contains the nginx image. This indicates that pushing images from Harbor to CR has succeeded.

Container Registry