Skip to main content
Compute, storage, and image registry resources are isolated across clusters. To use the same custom image in multiple clusters, configure an image registry synchronization policy. After synchronization is complete, development environments, training tasks, or inference services in the target cluster can select the image.

Create a Synchronization Policy

If the page indicates that no synchronization rule has been configured when you create an image, you can choose whether to synchronize it to other clusters. Once a synchronization rule is created, subsequently built images are synchronized to the target clusters according to the rule. The available regions and clusters depend on the current platform configuration.
  1. Go to Images > Custom.
  2. Open the Registry Synchronization Policy tab and click Create Policy.
  3. Configure the policy.
  4. After you configure the policy, click Create Policy.

View Synchronization Results

After creating the policy, you can view its details and execution information under Registry Synchronization Policy. Once synchronization is complete, check the Available Images list or the image details page to confirm that the target cluster has an available image URL. Use the image URL displayed for the target cluster. After synchronization, copy or select that URL; do not manually replace the source cluster’s registry domain. To verify that synchronization is working, check the following in order:

Frequently Asked Questions

First, check that the source and destination registries, tag-matching rules, and trigger type in the synchronization policy are correct. Then verify that the synchronization task was triggered and completed successfully. After synchronization, use the image URL displayed on the target cluster page.
No. It only indicates that existing instances have not been interrupted; it does not prove that new nodes can pull images from the target repository. Create a new environment or deploy a small-scale workload in the target cluster to confirm that the image can be pulled and started successfully.
Check the synchronization policy’s execution details. Where supported, you can also check Registry Events to see whether push, synchronization, or deletion events were generated or delivered.

Disable or Delete a Synchronization Policy

When a synchronization policy no longer needs to run automatically, you can disable or delete it from the policy list:
  • Disable: Stops automatic triggers for the policy while retaining its configuration, so you can re-enable it without having to configure it again. This is suitable for temporarily pausing cross-cluster synchronization.
  • Delete: Removes a synchronization policy that is no longer needed. Before deleting it, confirm that you will no longer need to synchronize images under this rule. Deleting the policy does not automatically delete images already synchronized to the target cluster.