检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Adjusting the DNS Configuration of the VPC and VM When the coredns add-on is started, it obtains the DNS configuration in the resolve.conf file from the deployed instance by default and uses the configuration as the upstream resolution server address. Before the coredns add-on is
Creating a CCE Turbo Cluster Using a Shared VPC Shared VPC Overview A shared VPC allows you to share your VPC resources with other accounts through the Resource Access Manager (RAM) service. For example, tenant A can share its VPC and subnets with tenant B. After tenant B accepted
VPC Network Settings VPC Network Model Expanding the Container CIDR Block of a Cluster That Uses a VPC Network Parent Topic: Container Networks
Connecting a Cluster to the Peer VPC Through an Enterprise Router Application Scenarios An enterprise router connects virtual private clouds (VPCs) and on-premises networks to build a central hub network and implement communication between VPCs in the same region. It has high specifications
If CCE nodes and other services are in different VPCs, you can use a peering connection or VPN to connect two VPCs. Note that the two VPC CIDR blocks cannot overlap with the container CIDR block.
Adding a Secondary VPC CIDR Block for a Cluster Scenario When creating a cluster, deploy it in a VPC. If the planned VPC is too small and IP addresses are insufficient, you can use a secondary VPC CIDR block to support your service scaling. This section describes how to add a secondary
Notes and Constraints To access a CCE cluster through a VPN, ensure that the VPN does not conflict with the VPC CIDR block where the cluster resides and the container CIDR block.
Expanding the Container CIDR Block of a Cluster That Uses a VPC Network Scenario If the container CIDR block configured during CCE cluster creation cannot meet service expansion requirements, you can add a container CIDR block for the cluster. Notes and Constraints This function is
Accessing Cloud Services from a Pod in the Same VPC The method of accessing cloud services from a pod in the same VPC varies depending on the cluster's network model. For details, see Table 1 Accessing cloud services from a pod in the same VPC. Table 1 Accessing cloud services from
Related Services CCE integrates with other services, including Elastic Cloud Server (ECS), Direct Connect, Virtual Private Network (VPN), and SoftWare Repository for Container (SWR). Figure 1 How hybrid cloud works Parent topic: Application Scenarios
In addition, in hybrid networking scenarios such as Direct Connect and VPN, communication between containers and hosts on the peer end can also be achieved with proper planning. Parent Topic: Networking
VPC Network Model Model Definition The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. In the VPC network
Creating a VPC and Subnet Context To provide a secure and isolated network environment for CCE, create a VPC before creating a cluster. If you have already created a VPC, you do not need to create it again. Creating a VPC On the management console, click Service List, and choose Network
ECS node specifications: CPU ≥ 2 cores, memory ≥ 4 GiB To access a CCE cluster through a VPN, ensure that the VPN CIDR block does not conflict with the VPC CIDR block where the cluster resides and the container CIDR block.
Related Services Software Repository for Container (SWR), Object Storage Service (OBS), Virtual Private Network (VPN) Figure 1 How DevOps works Parent topic: Application Scenarios
Direct Connect or VPN: To use images from an on-premises image repository, use Direct Connect or VPN to connect the on-premises network to the cluster's VPC. Once the network environment is connected to the VPC, no additional configuration is needed.
Creating a VPA Policy Kubernetes Vertical Pod Autoscaler (VPA) scales pods vertically. It does this by analyzing the historical usage of container resources and automatically adjusting the CPU and memory resources requested by pods. VPA can adjust container resource requests within
Accessing Cloud Services from a Pod in a Different VPC Pods cannot communicate with each other across VPCs. To resolve this issue, you can use VPC peering to connect two VPCs so that pods in one VPC can access services in the other VPC. The method of setting up cross-VPC connectivity
How Do I View the VPC CIDR Block? On the home page of the VPC console, view the Name/ID and CIDR Block of VPCs. You can modify the CIDR block of a VPC or re-create a VPC. Figure 1 Viewing the CIDR block of VPCs Parent Topic: Network Planning
Creating a VPA Policy Kubernetes Vertical Pod Autoscaler (VPA) scales pods vertically. It does this by analyzing the historical usage of container resources and automatically adjusting the CPU and memory resources requested by pods. VPA can adjust container resource requests within
