This topic describes the differences between Container Registry Personal Edition instances and Enterprise Edition instances.
Usage notes of Personal Edition instances
Container Registry Personal Edition is designed for individual developers. This edition is in public preview and is provided free of charge to a limited number of users. Alibaba Cloud does not provide a service level agreement (SLA) guarantee and SLA compensation for Container Registry Personal Edition and imposes limits on the use of the edition. The following section describes the differences between Personal Edition instances and Enterprise Edition instances. We recommend that you upgrade your instances to Enterprise Edition instances to experience the comprehensive features of Container Registry.
Container Registry Personal Edition is used only for development and testing. Do not use Container Registry Personal Edition in production environments.
Container Registry Personal Edition instances do not support API operations.
Differences between Personal Edition instances and Enterprise Edition instances
The following tables describe the features of Personal Edition instances and Enterprise Edition instances.
To learn how to select the edition that meets your business requirements and configure disaster recovery solutions, refer to the instance edition features and differences. Then follow the disaster recovery instructions to prepare a cross-zone disaster recovery solution, cross-region disaster recovery solution, and data backup solution.
Module | Feature | Personal Edition instance | Enterprise Edition instance | ||||
Basic Edition instance | Advanced Edition instance | ||||||
Disaster recovery | Instance | Cross-zone disaster recovery | None. | By default, multi-zone regions support this feature. | |||
Cross-region disaster recovery | None. | You must create multiple Container Registry instances in different regions to implement this feature. For more information, see Best practices for geo-disaster recovery of Container Registry Enterprise Edition instances. | |||||
Instance storage | Cross-zone disaster recovery | None. | You must use the zone-redundant storage (ZRS) feature of Object Storage Service (OSS) to implement this feature. For more information, see Create a zone-redundant storage bucket. | ||||
Cross-region backup | None. | You must use the cross-region replication (CRR) feature of OSS to implement this feature. For more information, see CRR. | |||||
Service guarantee | - | SLA | None. | 99.95% | 99.95% | ||
Ticks (
) indicate that the features are supported. Crosses (
) indicate that the features are not supported. Hyphens (-) indicate that the features are not applicable.
Module | Feature | Personal Edition instance | Enterprise Edition instance | Description | |||
Basic Edition instance | Advanced Edition instance | Personal Edition instance | Enterprise Edition instance | ||||
Artifact management | Container image | Hosting |
|
|
| - | - |
Namespace quota | 3 | 15 | 50 | For more information, see Manage namespaces. | |||
Public repository quota | 300 | 1000 | 5000 | For more information, see Create a repository and build images and Main features of a repository | |||
Private repository quota | |||||||
Virtual private cloud (VPC) quota for an access control list (ACL) |
| Purchase alone | - | ||||
Helm Chart | Hosting |
|
|
| - | For more information, see Push and pull Helm charts | |
Namespace quota |
| 15 | 50 | ||||
Public repository quota |
| 1000 | 5000 | ||||
Private repository quota | |||||||
OCI Artifact |
|
|
| - | For more information, Push and pull a custom OCI artifact | ||
Immutable image tags |
|
|
| For more information, see Configure a repository to be immutable | |||
Image tag management (automatic tag deletion) |
|
|
| For more information, Delete image tags | |||
Artifact building | Task quota for concurrent artifact building | 1 | 3 | 10 | - | - | |
Intelligent acceleration |
|
|
| - | For more information, see Use a Container Registry Enterprise Edition instance to build an image | ||
Multi-arch image building |
|
|
| - | For more information, see Build a multi-arch container image | ||
Artifact security | Artifact scanning by using multiple engines |
|
|
| - | - | |
Vulnerability fixing |
|
|
| - | - | ||
Risk blocking |
|
|
| - | For more information, see Create a delivery chain. | ||
Signing and signature verification |
|
|
| - | For more information, see Sign container images. | ||
Network access control |
|
|
| - | For more information, see Network access control overview. | ||
Operation audits |
|
|
| - | - | ||
Artifact distribution | Distribution performance (QPS of image pulling) | Not guaranteed | 250 | 1000 | - | - | |
Distribution in P2P mode |
|
|
| - | For more information, see Use P2P acceleration. | ||
On-demand distribution |
|
|
| - | For more information, see Load resources of a container image on demand. | ||
Image replication across regions around the world |
|
|
| - | For more information, see Replicate images within the same account and Replicate images between instances that belong to different accounts. | ||
Artifact subscription rules |
| 5 | 30 | - | - | ||
Artifact delivery | Trigger notifications |
|
|
| - | For more information, see Create an event notification rule. | |
Secret-free image pulls |
|
|
| For more information, see Push images to and pull images from an image repository of a Container Registry Personal Edition instance. | For more information, see Use the aliyun-acr-credential-helper component to pull images without using a secret. | ||
Cloud native application delivery chains |
|
|
| - | For more information, see Manage cloud native delivery chains. | ||
Instance management | Custom domain names |
|
|
| - | For more information, see Custom domain names. | |
Fast image migration from Harbor registries |
|
|
| - | For more information, see Migrate images from a self-managed Harbor instance to Container Registry Enterprise Edition within 10 minutes. | ||
