Container Registry
Container Registry
Document
- Documentation
Container RegistryContainer Registry (CR)User guideAccess configurationAccess controlConnecting VPCs across products
Copy page
Download PDFAccess control
Connecting VPCs across products
Copy pageDownload PDFConnecting VPCs across products
Standard Edition instances support connecting VPCs of different products within the same region, enabling cross-product intranet access. When you pull images and Helm Charts over the internal network, the push and pull speeds can be effectively improved, and public network bandwidth costs can be avoided.
warning
To establish the connectivity between a CR instance and a VPC, the private domain name of the instance needs to be resolved to an IP address within that VPC. Therefore, for each VPC you associate with an instance, one private domain name (PrivateZone) record and one elastic network interface (ENI) are automatically created for resolution. Private network resolution incurs fees. For billing details, see the Resolution request fees section in the TrafficRoute billing instructions.
Background
CR currently supports the following two types of VPCs.
- User VPC: Used to connect VPCs within the same region associated with this account. This enables internal network access across multiple VPCs, improving push and pull speeds, and eliminating public network bandwidth costs.
- Service VPC: Used to connect VPCs of other specified cloud products. This enables internal network access with other cloud products, improving push and pull speeds, and eliminating public network bandwidth costs.
Limits
- Only VPCs within the same region can be connected.
- The maximum total number of User VPCs (same account) and Service VPCs (cross-account) is 5. If you have reached this quota, delete any unnecessary VPC associations or request a quota increase. For instructions, see VPC access quota.
- Currently, only certain products support cross-product VPC authorization, such as veFaa.
Prerequisites
Service authorization for CR has been granted within the target cloud service.
Procedure
warning
Currently, only VPCs associated with the default security group named Default are supported. If the default security group name has been modified, change it back to Default before proceeding. To view the default security group of a VPC, see Viewing VPC details.
- Log in to the CR console.
- In the left navigation bar, click Instance list. On the right-side Instance list page, find the target Standard Edition instance, and click Enter instance.
- In the left navigation bar, click Access control. On the Access control page, click Add VPC.
- Configure the VPC to be added.
- ParameterDescriptionAccountSelect Cross-service. Select the authorized Volcano Engine account.VersionSelect New version, and select the VPC associated with another product.
- Click Confirm to complete the configuration.
Last updated: 2026.09.23 14:37:25
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
