Resource and Cost Planning
Figure 1 and Table 1 describe the resources required in this example and how they are related to each other.
Resource |
Specifications |
Description |
---|---|---|
CCE Autopilot cluster |
|
One cluster needs to be created. Cluster management and VPC endpoints are billed. For details, see Billing. |
Pod |
Jenkins master:
Jenkins agent:
|
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:
Pods are billed. For details, see Billing. |
ECS |
|
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 |
|
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 |
|
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. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot