Container Registry
Container Registry
Document
- Documentation
Container RegistryContainer Registry (CR)User guideAccess configurationAccess controlConnecting VPCs under the same account
Copy page
Download PDFAccess control
Connecting VPCs under the same account
Copy pageDownload PDFConnecting VPCs under the same account
CR supports connecting instances to VPCs under the same account, allowing resources in the VPC, such as ECS and VKE, to access an instance over the internal network. This enables high-speed and stable image push and pull while avoiding public network bandwidth costs.
tip
This operation is only applicable to Standard Edition instances.
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
VPC connectivity under the current account falls into the following two scenarios. In both scenarios, the VPC and the CR instance must be in the same account and region:
Limits
- Only VPCs in the same account and the same region can be connected.
- The total number of VPCs under the current account and cross-service VPCs cannot exceed 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 some products support cross-product VPC connectivity, such as machine learning platform, veFaaS, and ByteHouse Cloud Data Warehouse Version.
Prerequisites
- You have created a Standard instance. For instructions, see Creating Standard instances or Creating proxy cache registries.
- Connect a current-account VPC: You have created a VPC and a subnet in the same region. For instructions, see Creating VPCs and Creating subnets.
- Connect cross-product VPCs: Cross-service authorization for CR has been activated in the target product. The first time you use CR features in the target product, the system automatically displays the cross-service access request page. After you confirm the access role and the associated policy information, click Authorize now.
Connecting to the VPC of the current account
- Log in to the target instance.
- Log in to the CR console.
- Select the target region in the top navigation bar.
- In the left navigation pane, click Instance list. Select an entry point depending on your instance type:
- Standard instance: Click Standard instance. Find the target instance and click Enter instance.
- Proxy repository: Click Proxy cache. Click the target domain name to enter the instance details page.
- In the left navigation bar, click Access control. On the Access control page, click Add VPC.
- Configure the VPC to be added.
- ParameterDescriptionAccountSelect This account.Associated projectThe associated target project. After association, members of that project will inherit corresponding permissions for the CR services based on project authorization. For details, see Project management.VPCSelect an existing VPC. After the VPC is added, internal network push and pull of images and Helm charts are enabled among clusters in this VPC.SubnetSelect the VPC subnet to connect to. After configuration, resources within the selected subnet can access the instance via the private network to push or pull images.
- Click Confirm to complete the configuration.
Connecting VPCs across products
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 target instance.
- Log in to the CR console.
- Select the target region in the top navigation bar.
- In the left navigation pane, click Instance list. Select an entry point depending on your instance type:
- Standard instance: Click Standard instance. Find the target instance and click Enter instance.
- Proxy repository: Click Proxy cache. Click the target domain name to enter the instance details page.
- 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, and 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:21
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
