Synchronize Images to Other Regions or Repositories

If the service image is stored in a Region of the GPU Cloud, you can create a push rule to synchronize matching images to projects in other regions or to connected external repositories. Before synchronization, determine the source image repository path, tag scope, and target project to avoid synchronizing unnecessary versions.

​

Pre-Operation Confirmation

• Prepare the images to be synchronized in the source region.
• When synchronizing to an external repository, obtain the repository access address. If the repository requires authentication, obtain the corresponding credentials.

​

Connect an External Repository (Optional)

If the target is another region of the GPU Cloud, you can skip this section. You only need to add an external repository endpoint before synchronizing to an external repository.

1. Log in to the GPU Cloud console.
2. Go to STORAGE > Registry and select the region where the source image is located.
3. Open the Replication tab.
4. Click to expand the Registry Endpoints section, then click Add Endpoint.
5. Enter the external repository connection information.

   Configuration Item	Description
   Type	Select the external repository type.
   Name	Set the endpoint name to identify the external repository in replication rules. We recommend using a name that reflects the repository source or purpose.
   URL	Enter the public access address of the external repository, for example, https://example.com.
   Username	Enter this when the external repository requires authentication. Leave blank for public repositories.
   Password	Enter this when the external repository requires authentication. Leave blank for public repositories.

6. Click Confirm. The URL and credentials are validated upon submission. If the endpoint is unavailable, check the external repository address, network connectivity, username, and password before creating a synchronization rule. When synchronizing images between GPU Cloud regions, you do not need to add an external repository endpoint.

​

Create Synchronization Rule

1. On the Replication tab, click Create Replication Rule.
2. On the Create Sync Rule page, configure the synchronization rule. Basic information:

   Configuration Item	Description
   Sync Type	Select Push Mode to synchronize images from the current region to other regions or external repositories.
   Rule Name	Enter a rule name. Use a name that reflects the source project, destination, or synchronization scope to make the rule easy to identify in the rule list.
   Description	Enter a description for the rule as needed, such as the purpose of synchronization, the maintainer, or the applicable business.

   Source Registry:

   Configuration Item	Description
   Region	Select the Region where the source image is located.
   Namespace	Select the project to which the source image belongs.
   Repository	Select the image repository to synchronize.
   Tag (Regex)	Enter the tag matching criteria to synchronize. ** indicates that all tags are matched; 1.0* indicates that tags starting with 1.0 are matched. We recommend matching only the version range required by your business.

   Destination Registry:

   Configuration Item	Description
   Type	Select the target repository type. Local indicates synchronization to other regions of the GPU Cloud; Remote indicates synchronization to an integrated external repository.
   Registry Endpoint	Configure this when Remote is selected. Select an integrated external repository endpoint. If no endpoints are available, first integrate an external repository.
   Regions	Configure this when Local is selected. Select the target region that will receive the images.
   Namespace	Enter or select the target project. After synchronization is complete, the images will be written to this project.

   Synchronization Rules:

   Configuration Item	Description
   Override Mode	When enabled, resources with the same name in the target project will overwrite the resources on the target end. Before enabling it, confirm whether existing versions on the target end still need to be retained.
   Enable Rule	When enabled, the rule takes effect immediately after it is created. When not enabled, the rule is saved but synchronization will not start.
   Trigger Mode	Select a trigger method. Event-driven: Synchronization is triggered when a source image is pushed. Scheduled: Synchronization is performed periodically according to a Cron expression. Manual: The user manually triggers synchronization after creating the rule.
   Cron	Fill in this field when Scheduled is selected. The Cron expression uses UTC time. According to the page validation requirements, the first field must be 0, and the second field cannot be *. For example, 0 0 8 * * 1-5 indicates execution at 08:00 UTC every Monday through Friday.

3. Submit the rule and confirm that the new rule appears in the rule list. When using manual triggering, you also need to synchronize the rule once.

​

Confirm Synchronization Results

View the execution records for the corresponding rule on the Replication tab.

• If a task fails, view its logs and focus on checking the source image path, label matching, target project, and external repository connection.
• After successful execution, switch to the target region or target repository and confirm that the image has been added to the intended project.

​

Related Documentation

To import images from an external repository into the Registry in the current region, see Import Images from an External Repository.