On this page

Show all

Help Center/ Cloud Container Engine_Autopilot/ Best Practices/ Deploying Jenkins in a CCE Autopilot Cluster/ Resource and Cost Planning

Resource and Cost Planning

Updated on 2025-01-03 GMT+08:00

View PDF

Figure 1 and Table 1 describe the resources required in this example and how they are related to each other.

Figure 1 Solution architecture
Click to enlarge

Click to enlarge

**Table 1** Required resources and their prices
Resource	Specifications	Description
CCE Autopilot cluster	Cluster type: CCE Autopilot Billing mode: pay-per-use Cluster version: v1.28 Add-ons: CoreDNS and Kubernetes Metrics Server	One cluster needs to be created. Cluster management and VPC endpoints are billed. For details, see Billing.
Pod	Jenkins master: vCPUs: 4 Memory: 4 GiB Storage: 30 GiB Jenkins agent: vCPUs: 0.5 Memory: 1 GiB Storage: 30 GiB	Two pods are required, one for the Jenkins master and the other for the Jenkins agent. The functions of the two pods are as follows: The Jenkins master is responsible for job scheduling and system management. The Jenkins agent executes specific build jobs. Pods are billed. For details, see Billing.
ECS	Billing mode: pay-per-use VM type: General computing-plus Specifications: 2 vCPUs and 4 GiB of memory OS: CentOS 7.6 System disk: 40 GiB \| General purpose SSD EIP Type: exclusive EIP Bandwidth billing option: traffic Bandwidth: 5 Mbit/s	This ECS must be in the same VPC as the cluster. kubectl is installed on this ECS to deliver commands for creating workloads, PVs, PVCs, and secrets. After resources are created, you can delete the ECS in a timely manner to avoid extra expenditures. Deleting ECS does not affect the use of Jenkins. The ECS and EIP traffic are billed. For details, see ECS Billing.
SFS Turbo	Billing mode: pay-per-use Type: 40 MB/s/TiB Capacity: 1.2 TB	One SFS Turbo file system is required. SFS Turbo provides underlying storage resources for clusters so that you can use PVs and PVCs to provide persistent storage for workloads. SFS Turbo is billed. For details, see SFS Turbo Billing.
Load balancer provided by ELB	Billing mode: pay-per-use Type: dedicated load balancer Bandwidth billing option: traffic Bandwidth: 5 Mbit/s	One load balancer is required. The load balancer is used by the LoadBalancer Service to allow access to the workloads. ELB is billed. For details, see ELB Pricing Details.
SWR shared edition	-	One organization is required. SWR is used to store the images created in Building and Executing a Pipeline on Jenkins. Billing is not involved.

Parent Topic: Deploying Jenkins in a CCE Autopilot Cluster

Previous topic: Overview

Next topic: Procedure

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback

Log In and Submit Submit Cancel