Container Registry:Migrate self-managed Harbor to Container Registry Enterprise Edition

Step 1: Migrate the backend storage data

• If your Harbor registry uses File Storage NAS as its backend storage, you must first migrate the data to a bucket in Object Storage Service (OSS). For more information, see Tutorial: Migrate from NAS to OSS.

• If your Harbor registry uses a data center as its backend storage, use the OSS online migration service to migrate the data to an OSS bucket. For more information, see Case study: Migrate data from an on-premises data center to OSS.

• If your Harbor registry already uses Object Storage Service (OSS) for its backend storage, you can skip this step.

Step 2: Use a custom OSS bucket

When you create a Container Registry Enterprise Edition instance, you can specify a custom Object Storage Service (OSS) bucket as the instance's backend storage.

1. Create a RAM role for your account and grant it the necessary permissions to access the bucket. For more information, see Configure RAM access control for a custom OSS bucket.

2. Create a Container Registry Enterprise Edition instance.

   When you create the instance, set Instance Storage to Custom and select your bucket. For more information, see Create a Container Registry Enterprise Edition instance.

Step 3: Import images

1. Log on to the Container Registry console.

2. In the top navigation bar, select a region.

3. In the left-side navigation pane, click Instances.

4. On the Instances page, click the Enterprise Edition instance that you want to manage.

5. In the left-side navigation pane of the instance management page, choose Instances > Image Import.

6. On the Image Import page, click Trigger Task.

7. In the Tips dialog box, select Confirm to import, and then click Confirm.

   Note

   On the Image Import page, click Details in the Actions column to view an import task's progress.

Step 4: Configure a custom domain name

Container Registry Enterprise Edition supports custom domain names. This allows you to add a custom domain name and a corresponding SSL certificate to your instance, enabling access over HTTPS.

We recommend setting the custom domain name of your Container Registry Enterprise Edition instance to match the domain of your self-managed Harbor registry. For more information, see Access a Container Registry Enterprise Edition instance by using a custom domain name.