Updated on 2023-07-07 GMT+08:00

Typical Scenarios and Networking

Typical Scenarios

MCP can manage clusters of Huawei Cloud, other public clouds, and private clouds. It applies to the following scenarios:

Network Description

Before adding Kubernetes clusters to MCP, pay attention to network connections between MCP and each cluster. If both MCP and Kubernetes clusters have public IP addresses, ensure that they can communicate with each other using public IP addresses.

MCP can also manage Kubernetes clusters even though no public IP address is available. When creating an MCP instance, you can bind it to a hub VPC, which has a peering connection with the VPC where MCP resides. With the hub VPC, MCP can connect to a Kubernetes cluster in any of the following ways:

  • If the cluster is in the hub VPC and MCP is bound to the hub VPC, the cluster and MCP can communicate with each other.
  • If the cluster is in another VPC in the same region as MCP, you can create a peering connection between the VPC where the cluster resides and the hub VPC so that MCP and the cluster can communicate with each other.
  • If the cluster is in another public cloud or private network, you can use Direct Connect to connect the physical network to the hub VPC so that MCP and the cluster can communicate with each other.

MCP CIDR block, hub VPC CIDR block, and Kubernetes cluster CIDR block must not conflict with each other when a hub VPC is used. Otherwise, the cluster cannot be added.

Figure 1 Connecting to MCP through a hub VPC