If you manage container images in a self-built Harbor instance, you can migrate the images to Container Registry Enterprise Edition to reduce operations and maintenance (O&M) overhead, simplify integration with Container Service for Kubernetes (ACK), and streamline application delivery. Container Registry Enterprise Edition uses Object Storage Service (OSS) as its backend, so the migration preserves your existing data without requiring a full re-push of images.
Container Registry Enterprise Edition provides an enterprise-class secure service for managing container images and Helm charts. It supports distributing images to thousands of nodes concurrently and synchronizing images across regions on a global scale. The service also lets you create cloud-native application delivery chains to automatically deliver images globally upon source code changes. It is suitable for enterprise customers with high security requirements, multi-region deployments, and large-node clusters.
Prerequisites
Before you begin, make sure you have:
-
A self-managed Harbor instance with images to migrate
-
An OSS bucket, or permission to create one
-
A RAM role with permission to manage the OSS bucket — see Grant permissions to a RAM role that is used to access custom OSS buckets
-
(Optional) A custom domain name with an SSL certificate, if you want users to access the new registry using the same domain as the original Harbor instance
Step 1: Migrate Harbor backend data to OSS
Container Registry Enterprise Edition uses OSS as its backend storage. Before creating the instance, migrate your Harbor data to an OSS bucket based on where your Harbor data currently lives:
-
Harbor uses File Storage NAS — Migrate data from NAS to an OSS bucket. See Migrate data from NAS to OSS.
-
Harbor uses a local IDC (data center) — Use the OSS online migration service to transfer data from the data center to an OSS bucket. See Migrate data from a local IDC to OSS.
-
Harbor already uses OSS as backend storage — Skip this step.
Step 2: Create a Container Registry Enterprise Edition instance backed by the OSS bucket
When creating the instance, point it to the OSS bucket containing your Harbor data.
-
Attach a RAM role to your account and grant it permission to manage the target OSS bucket. See Grant permissions to a RAM role that is used to access custom OSS buckets.
-
Create a Container Registry Enterprise Edition instance. When configuring the instance, set Instance Storage to Custom and select the OSS bucket. See Create a Container Registry Enterprise Edition instance.
Step 3: Import images
After the instance is created with the OSS bucket as its backend, trigger the image import to index the existing images into the registry.
-
Log on to the Container Registry console.
-
In the top navigation bar, select a region.
-
In the left-side navigation pane, click Instances.
-
On the Instances page, click the Enterprise Edition instance you want to manage.
-
In the left-side navigation pane of the instance management page, choose Instances > Image Import.
-
On the Image Import page, click Trigger Task.
-
In the Tips dialog box, select Confirm to import and click Confirm.
After the task is created, click Details in the Actions column to monitor import progress.
Step 4: Bind a custom domain name
To let users access the new Container Registry Enterprise Edition instance using the same domain as the original Harbor instance, bind a custom domain name with an SSL certificate to the instance. After binding, the instance is accessible over HTTPS.
Set the custom domain name to match the domain name of the self-managed Harbor instance. See Use a custom domain name to access a Container Registry Enterprise Edition instance.