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 [email protected]

This chart will do the following:

• 1 x Jenkins Master with port 8080 exposed on an external LoadBalancer
• All using Kubernetes Deployments

To install the chart with the release name my-release:

$ helm install --name my-release stable/jenkins

The following tables lists the configurable parameters of the Jenkins chart and their default values.

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-release -f values.yaml stable/jenkins

Tip: You can use the default values.yaml

The Jenkins image stores persistence under /var/jenkins_home path of the container. A Persistent Volume Claim is used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.

• Enable Docker-in-Docker or Docker-on-Docker support on the Jenkins agents