> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Synchronize Images to Other Clusters

> Configure image registry synchronization policies in Siverse to distribute custom images to other clusters and view synchronization details and registry events.

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.

   | Configuration item | Description |
   | - | - |
   | Synchronization type | Select **Push Mode** or **Pull Mode**. **Push Mode** synchronizes images to other regions or external registries; **Pull Mode** pulls images from an external Registry. |
   | Policy name and description | Enter a policy name and add a description as needed to make the synchronization purpose easy to identify later. |
   | Source registry | Configure the source image registry information, including **Region**, **Namespace**, **Repository**, and **Tag (Regex)**. **Tag (Regex)** matches the image tags to synchronize. For example, `1.0*` matches tags that start with `1.0`. |
   | Destination registry | Configure the destination image registry information. Options for the destination type are **Local** and **Remote**. For **Local**, specify **Regions** and **Namespace**. |
   | Overwrite mode | Specify whether to overwrite resources with the same name at the destination. |
   | Enable policy | When enabled, the platform automatically synchronizes images according to the trigger rules. |
   | Trigger type | Select how the synchronization policy is triggered:<ul><li>**Event-driven**: Synchronization starts automatically when an image is pushed to the source registry.</li><li>**Scheduled**: Configure a Cron expression to trigger synchronization on a schedule.</li><li>**Manual**: After creating the policy, click the corresponding button in the policy list to trigger synchronization.</li></ul> |
   | Synchronize remote resource deletions | Enable this option as needed. Synchronization may delete associated images in the remote registry. Confirm the impact before proceeding. |

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:

| Check stage | Completion criteria |
| - | - |
| Policy configuration | Configure the source and destination registries, tag-matching rules, and trigger type to match expectations; only the images to be distributed should match. |
| Execution record | The synchronization task for the image has been triggered and completed successfully. |
| Target verification | The target cluster has a usable image URL that newly created development environments, training tasks, or inference services can pull. |

## Frequently Asked Questions

> **What should I do if an image builds successfully in the source cluster but cannot be pulled from the target cluster?**
>
> 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.

> **Does normal operation of existing containers mean that synchronization to the target cluster succeeded?**
>
> 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.

> **How can I tell whether a synchronization task was triggered?**
>
> 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.

## Related Documentation

* [Manage Custom Images](/siverse/images/manage-custom-images.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.