Jenkins helps users set up a continuous integration and continuous delivery environment. The Jenkins Master/Slave pod architecture can solve the pain points of concurrence restriction in batch building for enterprises, implementing continuous integration. This document describes how to use Jenkins in Tencent Cloud TKE to implement rapid and sustainable business delivery and reduce resource and labor costs.
The TKE-based Jenkins public network architecture is used as an example in this document. In this architecture, the Jenkins Master is located outside the TKE cluster and the slave pod is located within the TKE cluster. The diagram of the architecture is shown in the following figure:
This section describes the specific environment in this scenario.
Role | Kubernetes Version | Operating System |
---|---|---|
TKE managed cluster | 1.16.3 | CentOS 7.6.0_x64 |
Role | Version |
---|---|
Jenkins Master | 2.190.3 |
Jenkins Kubernetes plug-in | 1.21.3 |
Role | Private IP | Operating System | CPU | Memory | Bandwidth |
---|---|---|---|---|---|
Jenkins Master | 10.0.0.7 | CentOS 7.6 64-bit | 4 cores | 8 GB | 3 Mbps |
Node | 10.0.0.14 | CentOS 7.6 64-bit | 2 cores | 4 GB | 1 Mbps |
Complete the following steps to configure the TKE cluster and Jenkins. Then, use the slave pod to build, package, and publish the image into the TKE image repository. Lastly, use the pulled image for pod deployment in the TKE console.
Was this page helpful?