Jenkins is widely recognized as the most feature-rich CI available with easy configuration, continuous delivery and continuous integration support, easily test, build and stage your app, and more. It supports multiple SCM tools including CVS, Subversion and Git. It can execute Apache Ant and Apache Maven-based projects as well as arbitrary scripts.
$ helm install <helm-repo>/jenkins$ helm install bitnami/jenkins
This chart bootstraps a Jenkins deployment on a Kubernetes cluster using the Helm package manager.
Bitnami charts can be used with Kubeapps for deployment and management of Helm Charts in clusters. This Helm chart has been tested on top of Bitnami Kubernetes Production Runtime (BKPR). Deploy BKPR to get automated TLS certificates, logging and monitoring for your applications.
- Kubernetes 1.4+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
To install the chart with the release name my-release:
$ helm install --name my-release <helm-repo>/jenkins$ helm install --name my-release bitnami/jenkins The command deploys Jenkins on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
Tip: List all releases using
helm list
To uninstall/delete the my-release deployment:
$ helm delete my-releaseThe command removes all the Kubernetes components associated with the chart and deletes the release.
The following tables lists the configurable parameters of the Jenkins chart and their default values.
| Parameter | Description | Default |
|---|---|---|
global.imageRegistry |
Global Docker image registry | nil |
global.imagePullSecrets |
Global Docker registry secret names as an array | [] (does not add image pull secrets to deployed pods) |
image.registry |
Jenkins image registry | docker.io |
image.repository |
Jenkins Image name | bitnami/jenkins |
image.tag |
Jenkins Image tag | {VERSION} |
image.pullPolicy |
Jenkins image pull policy | Always if imageTag is latest, else IfNotPresent |
image.pullSecrets |
Specify docker-registry secret names as an array | [] (does not add image pull secrets to deployed pods) |
jenkinsUser |
User of the application | user |
jenkinsPassword |
Application password | random 10 character alphanumeric string |
jenkinsHome |
Jenkins home directory | /opt/bitnami/jenkins/jenkins_home |
disableInitialization |
Allows to disable the initial Bitnami configuration for Jenkins | no |
javaOpts |
Customize JVM parameters | nil |
service.type |
Kubernetes Service type | LoadBalancer |
service.port |
Service HTTP port | 80 |
service.httpsPort |
Service HTTPS port | 443 |
service.nodePorts.http |
Kubernetes http node port | "" |
service.nodePorts.https |
Kubernetes https node port | "" |
service.externalTrafficPolicy |
Enable client source IP preservation | Cluster |
service.loadBalancerIP |
LoadBalancer service IP address | "" |
ingress.enabled |
Enable ingress controller resource | false |
ingress.annotations |
Ingress annotations | [] |
ingress.certManager |
Add annotations for cert-manager | false |
ingress.hosts[0].name |
Hostname to your jenkins installation | jenkins.local |
ingress.hosts[0].path |
Path within the url structure | / |
ingress.hosts[0].tls |
Utilize TLS backend in ingress | false |
ingress.hosts[0].tlsHosts |
Array of TLS hosts for ingress record (defaults to ingress.hosts[0].name if nil) |
nil |
ingress.hosts[0].tlsSecret |
TLS Secret (certificates) | jenkins.local-tls-secret |
ingress.secrets[0].name |
TLS Secret Name | nil |
ingress.secrets[0].certificate |
TLS Secret Certificate | nil |
ingress.secrets[0].key |
TLS Secret Key | nil |
persistence.enabled |
Enable persistence using PVC | true |
persistence.storageClass |
PVC Storage Class for Jenkins volume | nil (uses alpha storage class annotation) |
persistence.accessMode |
PVC Access Mode for Jenkins volume | ReadWriteOnce |
persistence.size |
PVC Storage Request for Jenkins volume | 8Gi |
resources |
CPU/Memory resource requests/limits | Memory: 512Mi, CPU: 300m |
podAnnotations |
Pod annotations | {} |
metrics.enabled |
Start a side-car Jenkins prometheus exporter | false |
metrics.image.registry |
Jenkins exporter image registry | docker.io |
metrics.image.repository |
Jenkins exporter image name | tolleiv/jenkins_exporter |
metrics.image.tag |
Jenkins exporter image tag | latest |
metrics.image.pullPolicy |
Image pull policy | IfNotPresent |
metrics.image.pullSecrets |
Specify docker-registry secret names as an array | [] (does not add image pull secrets to deployed pods) |
metrics.podAnnotations |
Additional annotations for Metrics exporter pod | {prometheus.io/scrape: "true", prometheus.io/port: "9118"} |
metrics.resources |
Exporter resource requests/limit | Memory: 256Mi, CPU: 100m |
The above parameters map to the env variables defined in bitnami/jenkins. For more information please refer to the bitnami/jenkins image documentation.
Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
$ helm install --name my-release \
--set jenkinsUsername=admin,jenkinsPassword=password \
<helm-repo>/jenkins
$ helm install --name my-release \The above command sets the Jenkins administrator account username and password to admin and password respectively.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
$ helm install --name my-release -f values.yaml <helm-repo>/jenkins$ helm install --name my-release -f values.yaml bitnami/jenkins
Tip: You can use the default values.yaml
The Bitnami Jenkins image stores the Jenkins data and configurations at the /bitnami/jenkins path of the container.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. See the Configuration section to configure the PVC or to disable persistence.
Backwards compatibility is not guaranteed unless you modify the labels used on the chart's deployments. Use the workaround below to upgrade from versions previous to 1.0.0. The following example assumes that the release name is jenkins:
$ kubectl patch deployment jenkins --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'