OVH Guides

Install Jenkins on OVHcloud Managed Kubernetes

Find out how to install Jenkins on OVHcloud Managed Kubernetes

Last updated July 2nd, 2020.

In this tutorial we are going to guide you with the install of Jenkins on your OVHcloud Managed Kubernetes Service.

We are going to install Jenkins master and slave cluster utilizing the Jenkins Kubernetes plugin.

Before you begin

This tutorial presupposes that you already have a working OVHcloud Managed Kubernetes cluster, and some basic knowledge of how to operate it. If you want to know more on those topics, please look at the OVHcloud Managed Kubernetes Service Quickstart.

You also need to have Helm installer on your workstation and your cluster, please refer to the How to install Helm on OVHcloud Managed Kubernetes Service tutorial.

Installing the Jenkins Helm chart

[!warn] As with Helm 2, the official Helm stable repository is currently deprecated. The Helm community is currently transitioning to a hub model, with a Helm Hub, where charts can be searched using helm search hub <keyword> As most charts from the Helm stable repository have been transferred to the Bitnami repository we are using it in the tutorial.

For this tutorial we are using the Jenkins Helm chart found on Bitnami Helm repositories.

The chart is fully configurable, but here we are using the default configuration.

Customizing your install

Maybe you would like your admin username to be different, or be able to set your admin password, or modify the resources allocated...

In order to customize your install, without having to leave the simplicity of using helm and the Jenkins helm chart, you can simply set some of the configurable parameters of the Jenkins chart. Then you can add it to your helm install with the --set option (--set param1=value1,param2=value2)

helm install my-first-jenkins bitnami/jenkins

This will install your Jenkins mater:

$ $ helm install my-first-jenkins bitnami/jenkins
NAME: my-first-jenkins
LAST DEPLOYED: Thu Jul  2 14:09:06 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

1. Get the Jenkins URL by running:

** Please ensure an external IP is associated to the my-first-jenkins service before proceeding **
** Watch the status using: kubectl get svc --namespace default -w my-first-jenkins **

  export SERVICE_IP=$(kubectl get svc --namespace default my-first-jenkins --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}")
  echo "Jenkins URL: http://$SERVICE_IP/"

2. Login with the following credentials

  echo Username: user
  echo Password: $(kubectl get secret --namespace default my-first-jenkins -o jsonpath="{.data.jenkins-password}" | base64 --decode)

As the instructions say, you will need to wait a few moments to get the LoadBalancer URL. You can test if the LoadBalancer is ready using:

kubectl get svc --namespace default -w my-first-jenkins

After some minutes, you will get the LoadBalancer URL:

$ kubectl get svc --namespace default -w my-first-jenkins
NAME               TYPE           CLUSTER-IP    EXTERNAL-IP   PORT(S)                      AGE
my-first-jenkins   LoadBalancer   10.3.227.29   <pending>     80:32198/TCP,443:32750/TCP   2m13s
my-first-jenkins   LoadBalancer   10.3.227.29   XXXXXXX.lb...    80:32198/TCP,443:32750/TCP   2m13s

The URL under EXTERNAL-IP is your Jenkins URL. You can the follow the instructions on the Helm Chart to get the connection parameters. In my case:

$ export SERVICE_IP=$(kubectl get svc --namespace default my-first-jenkins --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}")

$ echo "Jenkins URL: http://$SERVICE_IP/"
Jenkins URL: XXXXXXX.lb...

$ echo Username: user
Username: user

$ echo Password: $(kubectl get secret --namespace default my-first-jenkins -o jsonpath="{.data.jenkins-password}" | base64 --decode)
Password: sdg84d7c34

And putting the URL in your browser will take you to the new Jenkins:

Jenkins login

Login with user admin and the password you got before. And ere you have your Jenkins:

Leeeeeeeroy Jenkins!

You have a working Jenkins on your OVHcloud Managed Kubernetes Service, congratulations!

Cleaning up

To clean up your cluster, simply use Helm to delete your Jenkins release.

helm delete my-first-jenkins

It will delete your Jenkins and its associated resources from your cluster:

$ helm delete my-first-jenkins
release "my-first-jenkins" uninstalled

These guides might also interest you...