Container Registry
Container Registry
Container Registry
Document
Container Registry (CR)
What's new
Overview
Billing
Billing item
Getting started
User guide
User authorization
Authorization management
Robot account management
Instance management
Namespace management
OCI artifact repository management
OCI artifact management
Version management
Tag immutability rule management
Tag retention rules management
Access configuration
Access control
Distribution acceleration
P2P acceleration
Image lazy loading
Registry replication
Audit log management
Alerts and notifications
Best practices
Image push and pull
Image migration and synchronization
DevOps delivery
FAQ
Authorization
VPC
Image push and pull
Limits
Registry replication
P2P acceleration
Access control
API
Calling Method
Instance Management
Namespace Management
OCI Artifact Repository Management
OCI Artifact Version Management
Domain Management
Access Endpoint Management
Temporary Access Key
Robot Account Management
General Data Structure
Artifact repository AR
What's new
Product overview
Getting started
User guide
Instance management
Repository Management
Access control
Permanent access credentials
Temporary access credentials
Maven package management
Generic package management
PyPI package management
NPM package management
Uploading packages
Downloading packages
AI package management
Permission management
API Reference
Repository Management
Package management
Version Management
File Management
Temporary Key Management
General Data Structure
- Documentation
Container RegistryContainer Registry (CR)User guideRegistry replicationRegistry replication overview
Copy page
Download PDFRegistry replication
Registry replication overview
Copy pageDownload PDFRegistry replication overview
Registry replication is an image distribution capability provided by Container Registry (CR). It supports automatic replication of images and Helm charts across instances, regions, and repositories to meet the requirements of scenarios such as multi-region deployment, disaster recovery, and migration.
tip
This operation is supported for Standard Edition instances only and is not supported for proxy cache registries.
Feature overview
Registry replication automatically or manually replicates images and Helm charts from a source repository to a destination repository based on replication rules. After a replication rule is created, the system automatically triggers a replication task whenever a new image is pushed to the source repository and matches the rule. You can also manually trigger a full replication.
Replication types
CR supports the following replication types for different scenarios:
Replication type | Description | Source | Destination |
Replication type | Description | Source | Destination |
Replicates images between Standard Edition instances under the same Volcano Engine account, either within the same region or across regions. This type applies to scenarios such as multi-region deployment, disaster recovery, and backup. | Standard Edition instance | Standard Edition instance (same account) | |
Replicates images from a CR Standard Edition instance to an external self-hosted registry, such as a self-hosted Harbor registry or a registry provided by another cloud service provider. This type applies to scenarios such as hybrid cloud deployment and cross-cloud distribution. | Standard Edition instance | External registry, such as Harbor, ACR, or ECR | |
Replicates images and Helm charts from a third-party registry to a CR instance. This type applies to scenarios such as image migration and unified management of external images. | External registry, such as AWS ECR, Harbor, or Docker Hub | Standard Edition instance or Micro Edition instance |
Limits
- Supported artifact types: Docker images and Helm charts.
- Each account supports a maximum of 5 enabled registry replication rules at the same time.
- After a rule is deleted, historical logs cannot be viewed.
- By default, the last 1,000 synchronization logs are retained for each rule.
- Once a registry replication rule is triggered, the current synchronization task cannot be terminated.
Last updated: 2026.09.23 14:37:25
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
