Jenkins Helm Chart
Jenkins master and slave cluster utilizing the Jenkins Kubernetes plugin
- https://wiki.jenkins-ci.org/display/JENKINS/Kubernetes+Plugin
Inspired by the awesome work of Carlos Sanchez carlos@apache.org
This chart is fully based on the chart found at the Kubernetes Charts.
Chart Details
This chart will do the following:
- 1 x Jenkins Master with port 80 exposed on an external LoadBalancer
- All using Kubernetes Deployments
Right now, we are using Jenkins 2.73.1.
Get this chart
Our central repository is located at: https://devopsku.be/charts, please configure this in your helm installation (via helm repo add). Then you can download and install this chart using the usual helm procedure (see Using Helm).
If you would like to contribute and/or like to make changes on this chart, please clone this repo via:
git clone https://github.com/devopskube/devopskube.git
Installing the Chart
The installation-instructions can be found on the above mentioned Using Helm page.
Configuration
The following tables lists the configurable parameters of the Jenkins chart and their default values.
Jenkins Master
| Parameter | Description | Default |
|---|---|---|
master.name |
Jenkins master name | jenkins-master |
master.image |
Master image name | gcr.io/kubernetes-charts-ci/jenkins-master-k8s |
master.imageTag |
Master image tag | v0.1.0 |
master.imagePullPolicy |
Master image pull policy | Always |
master.vomponent |
k8s selector key | jenkins-master |
master.cpu |
Master requested cpu | 200m |
master.memory |
Master requested memory | 256Mi |
master.servicePort |
k8s service port | 80 |
master.containerPort |
Master listening port | 8080 |
master.slaveListenerPort |
Listening port for agents | 50000 |
master.adminUser |
The initial admin user | admin |
master.adminPassword |
The initial admin user password | admin1234 |
master.javaOpts |
Some java options | -Xms512m -Xmx512m |
master.hostName |
The hostName of the jenkins instance | jenkins.example.com |
master.systemMessaage |
The Systemmessage | DevOpsKube Build Server |
persistence.path |
The path where data is stored | /data/jenkins |
Jenkins Agent
| Parameter | Description | Default |
|---|---|---|
agent.image |
Agent image name | jenkinsci/jnlp-slave |
agent.imageTag |
Agent image tag | 2.52 |
agent.cpu |
Agent requested cpu | 200m |
agent.memory |
Agent requested memory | 256Mi |
Other Settings
| Parameter | Description | Default |
|---|---|---|
smtp.host |
Smtp Host | mail.example.com |
smtp.port |
Smtp Host Port | 999 |
smtp.replyTo |
The replyTo Address | buildmaster@example.com |
smtp.auth.userName |
The username to authenticate on the smtp server | buildmaster@example.com |
docker.account |
Docker Registry Login | yourUserName |
docker.password |
Docker Registry Password | yourPassword |
Specify each parameter using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install --name my-jenkins -f values.yaml jenkins-x.x.x.tgz
Tip: You can use the default values.yaml Tip: Initial Username/Password is (as listed above) admin/admin1234.
Persistence
To be able to keep stateful data in the jenkins kubernetes container, the following path is used:
/data/jenkins
Right now, we do use HostPathes, which do not work in a real cluster environment (like AWS or GCE). Please adopt this one to your own needs.
Login Url
http://jenkins.devopskube.org/loginEntry?from=%2F
Todo
Enable Docker-in-Docker or Docker-on-Docker support on the Jenkins agentspre-start script- Add SSO
- Use persistence volume claims
- install needs volume on host (with correct rights
sudo chown 1000:1000 jenkins) - Document clearer that right now the usage of the jenkins-jnlp-slave docker image is moved to the Jenkinsfile (or even better: use it in the central config, and delete it from the Jenkinsfiles)
- Provide additional slaves, like needed (building charts, building nodejs stuff)