Resource Planning

In this example, you need to create a VPC, an ECS, a CCE cluster, and a VPC peering connection. For details about the resource planning, see Table 1.

The following resource planning details are only examples for your reference. You need to plan resources based on actual service requirements.

**Table 1** Resource and cost planning
Resource	Description
VPC	In this example, there are three VPCs, including the VPC where the ECS resides and the VPC where the testing cluster and production cluster reside. These VPCs are located in the same region, and the subnet CIDR blocks of these VPCs do not overlap. vpc-X: 192.168.0.0/16 (VPC where the ECS with GitLab and Jenkins installed resides) vpc-A: 172.16.0.0/16 (VPC to which the testing cluster resides) vpc-B: 172.17.0.0/16 (VPC where the production cluster resides)
ECS	In this example, there is one ECS located in vpc-X (with CIDR block of 192.168.0.0/16). Node flavor: 4 vCPUs \| 16 GiB OS: Huawei Cloud EulerOS 2.0 EIP: An EIP is automatically created for the node to access the public network and pull images.
CCE cluster	In this example, there are two CCE clusters, including the testing and production clusters. The following lists some key parameter configurations. (You can configure other parameters as required or use their default values.) Cluster type: CCE Turbo cluster VPC: The testing cluster is located in vpc-A (172.16.0.0/16), and the production cluster is located in vpc-B (172.17.0.0/16). Actual number of nodes: 1 per cluster Node configurations: Node flavor: 4 vCPUs \| 16 GiB OS: Huawei Cloud EulerOS 2.0 EIP: An EIP is automatically created for the node to access the public network and pull images.
VPC peering connection	In this example, there are two VPC peering connections. The network connection requirements are as follows: peer-XA: connects vpc-X to vpc-A. peer-XB: connects vpc-X to vpc-B.