Table of contents

CloudBees Core Reference Architecture - Kubernetes

Kubernetes on-premise and OpenShift

This document is designed to help you ensure that your on-premise or private-cloud Kubernetes cluster is optimally configured for running CloudBees Core in a secure and efficient way.

Most of the content in this document applies to OpenShift, except for the Securing Network Communication section. If you’re using OpenShift, substitute oc for kubectl.

This document includes the following topics:

For more information on Kubernetes please refer to the official Kubernetes Documentation.

Terms and Definitions


Jenkins is an open-source automation server. Jenkins is an independent open-source community, to which CloudBees actively contributes. You can find more information about Jenkins and CloudBees contributions on the CloudBees site.

CloudBees Core

Commercial version of Jenkins based on Jenkins Long-Term Support (LTS) releases with frequent patches by CloudBees. CloudBees Core also provides a number of plugins that help organizations address main needs of enterprise installations: Security, Continuous Delivery, etc.

CloudBees Core Operations Center

operations console for Jenkins that allows you to manage multiple Jenkins masters. See details on the CloudBees site.

Architectural Overview

This section provides a high-level architectural overview of CloudBees Core, designed to help you understand how CloudBees Core works, how it integrates with Kubernetes, its network architecture and how Managed Masters and build agents are provisioned.

CloudBees Core is essentially a set of Docker Containers that can be deployed to run a cluster of machines within the Kubernetes container management system. Customers are expected to provision and configure their Kubernetes system before installing CloudBees Core.

CloudBees Core includes the CloudBees Core Operations Center that provisions and manages CloudBees Managed Masters and Team Masters. CloudBees Core also enables Managed Masters and Team Masters to perform dynamic provisioning of build agents via Kubernetes.

Machines and Roles

CloudBees Core is designed to run in a Kubernetes cluster. For the purposes of this section, you need to know that a Kubernetes cluster is a set of machines (virtual or bare-metal), which run Kubernetes. Some of these machines provide the Kubernetes control plane as Kubernetes Masters. They control the Containers that run on the other type of machines known as Kubernetes Nodes. The CloudBees Core containers will run on the Kubernetes Nodes.

The Kubernetes Masters provide an HTTP-based API that can be used to manage the cluster, configure it, deploy containers, etc. A command-line client called kubectl can be used to interact with Kubernetes via this API. You should refer to the Kubernetes documentation for more information on Kubernetes.

CloudBees Core Docker Containers

The Docker containers in CloudBees Core are:

  • cloudbees-cloud-core-oc: CloudBees Core Operations Center

  • cloudbees-core-mm: CloudBees Core Managed Master

The Docker containers used as Jenkins build agents are specified on a per Pipeline basis and are not included in CloudBees Core. Refer to the example Pipeline in the Agent Provisioning section for more details.

The cloudbees-cloud-core-oc, cloudbees-core-mm and build agent container images can be pulled from the public Docker Hub repository or from a private Docker Registry that you deploy and manage. If you wish to use a private registry, you will have to configure your Kubernetes cluster to do that.

CloudBees Core Kubernetes Resources

The cloudbees-core.yml configuration file defines the set of required Kubernetes resources for CloudBees Core.

How cloudbees-core.yml is applied

When CloudBees Core is deployed to a Kubernetes cluster, cloudbees-core.yml is apolied using the command

$ kubectl create -f yaml-configuration-file-name

Upon deployment, CloudBees Core creates and runs a Pod called cjoc which contains a Container called cjoc. You can log into Operations Center and provision Managed Masters to run your Pipelines.

Kubernetes terminology

The following terms are useful to understand. This is not a comprehensive listing: for full details on these and other terms, see the Kubernetes documentation.


A set of containers that share storage volumes and a network interface.


Defines an account for accessing the Kubernetes API.


Defines a set of permission rules for access to the Kubernetes APIs.


Binds a ServiceAccount to a Role.


A directory of configuraton files made available on all Kubernetes Nodes.


Managing deployment and scaling of a set of Pods.


Provides access to a set of Pods at one or more TCP ports.


Uses hostname and path of an incoming request to map the request to a specific Service.

CloudBees Core Kubernetes resources

cloudbees-core.yml defines the following Kubernetes resources:

Resource type Resource value Definition



Account used to manage Jenkins Build Agents.



Account used by Operations Center to manage Managed Masters.



Defines permissions needed by Operations Center to manage Jenkins Masters.



Binds the Operations Center ServiceAccount to the master-management Role.



Binds the jenkins ServiceAccount to the pods-all Role.



Defines the configuration used to start the cjoc Java process within the cjoc Container.



Defines location.groovy, which is executed on startup by cjoc to define its own hostname.



Defines the Bash script that starts the Jenkins Agent within a Build Agent Container.



Defines a Pod for the cjoc Container, allocates a persistent volume for its JENKINS_HOME directory and ensures that one such Pod is always running.



Defines a Service front-end for the cjoc Pod and assigns TCP ports 80 and 50000 to JNLP.



Maps requests for the CloudBees Core hostname and the path /cjoc to the cjoc Pod.



Maps requests for the CloudBees Core hostname to the path /cjoc.

Setting pod resource limits

You can specify default limits in Kubernetes namespaces. These default limits will constrain the amount of CPU or memory a given Pod can use unless the defaults are explicitly overridden by the Pod’s configuration.

For example, the following configuration limits requests running in the master-0 namespace to 256 MB of memory and total memory usage to 512 MB:

apiVersion: v1
kind: LimitRange
  name: mem-limit-range
  namespace: master-0
  - default:
      memory: 512Mi
      memory: 256Mi
    type: Container

Overriding default pod resource limits

To override the default configuration on a pod-by-pod basis, configure the master that needs more resources:

  1. Log into CloudBees Core Operations Center.

  2. Navigate to Manage Jenkins  Kubernetes Pod Templates.

  3. Select menu:Add a pod template.

    1. Locate the template you want to edit.

    2. If the template you want to edit does not exist, create it.

  4. On the Containers tab, click menu:Add Containers and select container.

  5. Click menu:Advanced and modify the resource constraints for the template.

Visualizing CloudBees Core Architecture

The diagram below illustrates the CloudBees Core architecture on Kubernetes. The diagram shows three Kubernetes Master Nodes, which are the three dotted-line and overlapping rectangles on the left. The diagram also shows two Kubernetes Worker Nodes, which are the two dotted-line large rectangles in the center and right.

Here’s the key for the colors used in the diagram:

  • Green: processes which are part of Kubernetes

  • Pink: Kubernetes resources created by installing and running CloudBees Core

  • Yellow: Kubernetes resources required by CloudBees Core

Architecture diagram
Figure 1. CloudBees Core Architecture

Kubernetes Master

Running on each Kubernetes Master node, there are the Kubernetes processes that manage the cluster: the API Server, the Controller Manager and the Scheduler. In the bottom left of the diagram are resources that are created as part of the CloudBees Core installation, but that are not really tied to any one node in the system.

Kubernetes Nodes

On the Kubernetes Nodes and shown in green above is the kubelet process, which is part of Kubernetes and is responsible for communicating with the Kubernetes API Server and starting and stopping Kubernetes Pods on the Node.

On one Node, you see the Operations Center Pod which includes a Master Provisioning plugin that is responsible for starting new Master Pods. On the other node you see a Master Pod, which includes the Jenkins Kubernetes Plugin and uses that plugin to manage Jenkins Build Agents.

Each Operations Center and Master Pod has a Kubernetes Persistent Volume Claim where it stores its Jenkins Home directory. Each Persistent Volume Claim is backed by some form of storage service, such as an EBS volume on AWS or an NFS drive in an OpenShift environment. When a Master Pod is moved to a new Node, its storage volume must be detached from its old Node and then attached to the Pod’s new node.

Pod scheduling best practice

As a best practice, insure Kubernetes schedules build agent pods on the same nodes that are not running CloudBees Core Operations Center and Managed Masters. This is accomplished using Kubernetes taints and tolerations and Kubernetes labels and node selectors. The taints and labels should be added to the Kubernetes nodes before deploying CloudBees Core onto the cluster.

Use kubectl to apply taints and labels to nodes.

Use the following commands, kubectl taint nodes <node name> <key>=<value>:<effect> and kubectl label nodes <node name> <label-key>=<label-value>. For example kubectl taint nodes node1 dedicated=master-node:NoSchedule and kubectl label nodes node1 dedicated=master-node.

Only pods with a toleration in their spec that matches the key, value, and effect can be scheduled on the tainted nodes, only pods with nodeSelector property matching a node’s label will be scheduled on those nodes. These combine to make sure CloudBees Core Operations Center and Managed Masters are scheduled only on the nodes dedicated to them and that build agents are not scheduled on those nodes. The pod spec for CloudBees Core Operations Center and Managed Masters need to be scheduled on the example node1.

kind: StatefulSet
        dedicated: master-node
      - key: "dedicated"
        operator: "Equal"
        value: "master-node"
        effect: "NoSchedule"

The nodeSelector property can also be set in the Kubernetes Master Provisioning Plugin UI. In CloudBees Core Operations Center Manage Jenkins > Configure System > Kubernetes Master Provisioning > Advanced.


Making sure the pod templates for build agents do not have this toleration will prevent build agents from being scheduled on the tainted nodes.

Prevent CloudBees Core Operations Center and Managed Masters pods from being moved during scale down operations by adding the annotation "false"

kind: StatefulSet
      annotations: "false"`

Master Provisioning

One of the benefits of CloudBees Core is the easy provisioning of new Jenkins Managed masters from the Operations Center web interface. This feature is provided by the CloudBees Core Master Provisioning Plugin for Jenkins. When you provision a new master, you must specify the amount of memory and CPU to be allocated to the new master, and the provisioning plugin will call upon the Kubernetes API to create a master.

The diagram below shows what happens when a new Master is launched via Operations Center. First, CJOC’s Master Provisioning Kubernetes Plugin calls Kubernetes to provision a new StatefulSet to run the Managed Master Pod.

Master Provisioning Diagram
Figure 2. Master Provisioning

Agent Provisioning

Agents are created and destroyed in CloudBees Core by the Jenkins Kubernetes Plugin. A Jenkins Pipeline can specify the build agent using the standard Pipeline syntax. For example, below is a CloudBees Core Pipeline that builds and tests a Java project from a GitHub repository using a Maven and Java 8 Docker image:

Pipeline Example
podTemplate(label: 'kubernetes',
  containers: [
    containerTemplate(name: 'maven', image: 'maven:3.5.2-jdk-8-alpine', ttyEnabled: true, command: 'cat')
  ]) {
  stage('Preparation') {
    node("kubernetes") {
      container("maven") {
        git '';
        sh "mvn -Dmaven.test.failure.ignore clean package"
        junit '**/target/surefire-reports/TEST-*.xml'
        archive 'target/*.jar'

In the above example, the build agent container image is maven:3.5.2-jdk-8-alpine. It will be pulled from the Docker Registry configured for the Kubernetes cluster.

The diagram below shows how build agent provisioning works. First, when the Pipeline runs, the Kubernetes Plugin on the Managed Master calls Kubernetes to provision a new pod to run the build agent container. Second, Kubernetes launches the build agent pod to execute the Pipeline.

Agent Provisioning Diagram
Figure 3. Agent Provisioning

CloudBees Core Required Ports

CloudBees Core requires open ports:

  • 80 for http access to the web interface of Operations Center and Managed Masters

  • 443 for https access to the web interface of Operations Center and Managed Masters

  • 50000 for Java Network Launch Protocol (JNLP) access to Operations Center and Managed Masters

Refer to the Kubernetes documentation for its port requirements.

Network Encryption

Network Communication between Kubernetes clients such as kubectl, Kubernetes masters and nodes is encrypted via TLS protocol. The Kubernetes Managing TLS in a Cluster document explains how Certificates are obtained and managed by a cluster.

Communication between application containers running on a Kubernetes cluster, such as Operations Center and Managed Masters, can be encrypted as well but this requires the deployment of a Network Overlay technology such as Weave Works. End-to-end Web Browser to CloudBees Core communications can be TLS encrypted by configuring the Kubernetes Ingress that provides access to CloudBees Core to be the termination point for SSL. Network Overlay and SSL termination configuration is covered in a separate section.

High Availability

Kubernetes can be configured for high availability by using at least three Kubernetes Masters on three separate machines in different Availability Zones.


Operations Center and Managed Masters store their data in file-system directory, known as Jenkins Home. Operations Center has its own Jenkins Home, and each Master also has one.

CloudBees Core uses a Kubernetes feature known as Persistent Volume Claims to dynamically provision persistent storage for Operations Center, each Managed Master and build agents.

Cluster Sizing and Scaling

This document provides general recommendations about sizing and scaling a Kubernetes cluster for CloudBees Core starting with some general notes about minimum requirements and ending with a table of more concrete sizing guidelines recommended by CloudBees.

General notes

When sizing and scaling a cluster you should consider the operational characteristics of Jenkins. The relevant ones are:

  • Jenkins Masters are memory and disk IOPS bound, with some CPU requirements as well. Low IOPS results into longer startup times and worse general performance. Low memory results into slow response time.

  • Build Agents requirements depend on the kind of tasks being executed on them.

Pods are defined by their CPU and memory requirement and they can’t be split across multiple hosts.

It is recommended to use hosts that are big enough so that they can host several pods (Rule of thumb : 3-5 pods per host) at the same time to maximize their actual use.

Example: You are running builds requiring 2 GB of memory each. You need configure pods to have 2 GB each for supporting such builds. The rule of thumb says you should have hosts with 6-10 GB of memory (3 x 2 - 5 x 2).

Depending on your cloud provider, it may be possible to enable auto-scaling in Kubernetes to match with the actual requirements and reduce the operational costs.

If you don’t have auto-scaling in your environment, we recommend you to plan extra capacity in order to sustain hardware failure.


Each Managed Master is provisioned on a separate Persistent Volume (PV). It is recommended to use a storage class with the most IOPS available.

The host storage is not getting used by Managed Masters but depending on the instance type you may have restrictions on the kind of block storage you can use (for example, on Azure, you need to use an instance type ending with s).

Disk space on the hosts is necessary to host docker images, containers and volumes. Build workspaces will be on host storage so there must be enough free disk space available on nodes.


CloudBees Core uses the notion of CPU defined by Kubernetes.

By default, a Managed Master requires 1 CPU. Each build agent also requires CPU, so what will determine the total CPU requirement is :

  • (mostly static) The number of Managed Masters multiplied by the number of CPU each of them requires.

  • (dynamic) The number of concurrent build agents used by the cluster multiplied by the CPU requirement of pod template. A minimum amount of 1 CPU is recommended for a pod template but you can use more cpus if parallel processing is required by the task.

Most build tasks are CPU-bound (compilation, test executions). So it is quite important when defining pod templates not to underestimate the number of cpus to allocate if you want good performance.


By default, a Managed Master requires 3 GB of RAM.

To determine the total memory requirement, take into account:

  • (mostly static) The number of Managed Masters multiplied by the amount of RAM each of them requires.

  • (dynamic) The number of concurrent build agents used by the cluster multiplied by the memory requirement of pod template

Memory also impacts performance. Not giving enough memory to a Managed Master will cause additional garbage collection and reduced performance.

Master Sizing Guidelines

Below are some more concrete sizing guidelines compiled by CloudBees Support Engineers:

Table 1. Master sizing guidelines
Requirement Baseline Rationale

Team Size


Most agile resources warn against going above 10 team members. Keeping the team size at 10 or below facilitates the sharing of knowledge about Jenkins and pipeline best practices.Three items

Average Weekly Users


Besides the team themselves, other non-team collaborators often must access the team’s Jenkins to download artifacts or otherwise collaborate with the team. This includes API clients.

Serving the Jenkins user interface impacts IO and CPU consumption and will also result in increased memory usage due to the caching of build results.

CPU Cores


A Jenkins of this size should have at least 4 CPU cores available.

Maximum Concurrent Builds


Healthy agile teams push changes multiple times per day and may have a large test suite including unit, integration and automated system tests.

We generally observe Jenkins easily handles up to 50 simultaneous builds, with some Jenkins regularly running many multiples of this number. However, poorly written or complicated pipeline code can significantly affect the performance and scalability of Jenkins since the pipeline script is compiled and executed on the master.

To increase the scalability and throughput of your Jenkins master, we recommend that Pipeline scripts and libraries be as short and simple as possible. This is the number one mistake teams make. If build logic can possibly be done in a Bash script, Makefile or other project artifact, Jenkins will be more scalable and reliable. Changes to such artifacts are also easier to test than changes to the Pipeline script

Maximum Number of Pipelines (Multi-branch projects)


Well-designed systems are often composed of many individual components. The microservices architecture accelerates this trend, as does the maintenance of legacy modules.

Each pipeline can have multiple branches, each with its own build history. If your team has a high number of pipeline jobs, you should consider splitting your Jenkins further.

Recommended Java Heap Size

4 GB

We regularly see Jenkins of this size performing well with 4 gigabytes of heap. This means setting the -Xmx4g as recommended in option B of our KB article on the topic.

If you observe that your Jenkins instance requires more than 8 gigabytes of heap, your Jenkins likely needs to be split further. Such high usage could be due to buggy pipelines or perhaps non-verified plugins your teams may be using.

AWS Auto-scaling groups

With a cluster set up on AWS (including EKS), it is possible to define one or several auto-scaling groups. This can be useful to assign some pods to specific nodes based on their specification.


There is an issue where the AWS Auto Scaling group can move nodes to another Availability Zone, which can cause problems with the Kubernetes Cluster Autoscaler resulting in unexpected pod terminations.

There are two solutions:

  1. Suspend AZRebalance on Auto Scaling groups to keep nodes from changing Availability Zones.

  2. Use one Availability Zone on Auto-Scaling Groups, however this will reduce fault tolerance

Targeting specific nodes / segregating pods

When defining pod templates using the Jenkins Kubernetes plugin, it is possible to assign pods to nodes with particular labels.

For example, the below pipeline code would create a pod template restricted to instance type m4.2xlarge.

def label = "mypod-${UUID.randomUUID().toString()}"
podTemplate(label: label, containers: [
    containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', ttyEnabled: true, command: 'cat'),
    containerTemplate(name: 'golang', image: 'golang:1.8.0', ttyEnabled: true, command: 'cat')
  nodeSelector: '') {
  node(label) {
    // some block

If you are configuring a Kubernetes Pod Template using the Jenkins UI, you can select this option under the Node Selector field (press the Advanced button at the end of the pod template to reveal this option).

Assigning pods to particular nodes is very useful if you wish to use particular instance types for certain types of workloads.

Please read Assigning Pods to Nodes to understand this feature more in details.

It is not yet possible to restrict the nodes on which masters are assigned.

Setting up a Private and Encrypted Network

Use a Private and Encrypted Network to ensure that all network communication between the CloudBees Core Operations Center, Managed Masters and Build Agents is encrypted.

Network communication between the Kubernetes components running on Kubernetes Masters and Kubernetes nodes is encrypted using the TLS protocol. Each Kubernetes cluster includes a Certificate Authority (CA) that it uses to create and validate the TLS certificates used when Kubernetes components communicate with the Kubernetes API server. Refer to the Kubernetes documentation page Manage TLS Certificates in a Cluster for more information.

Applications deployed to a Kubernetes cluster, such as CloudBees Core, are not protected by Kubernetes built-in TLS encryption. To ensure that all network communication between application components is encrypted, configure your Kubernetes cluster to use a Network Policy Provider that supports encryption. The Kubernetes documentation Declare Network Policy page lists the providers that are supported.

Select a Network Policy Provider: Weave Net

The CloudBees Core development team has had some experiences using Weave Net with Kubernetes, but has not deployed Weave Net in production, so Weave Net is only our preliminary recommendation. We selected Weave Net for this document because of those experiences and because Weave Net uses IPSec protocol and its encryption uses the well-known NaCl library.

Weave Net is open source software licensed under the Apache Software Licence v2 and developed by Weaveworks with source code hosted at the Weave GitHub project. You can read more about the product and its requirements on the Weave Net overview page.

The Kubernetes documentation page Weave Net for Network Policy explains how to setup Weave and additional details are provided at the Weave Net documentation page Integrating Kubernetes via the Addon.

The rest of this section gives an outline of the steps you need to take to configure Weave Net to use encryption. In summary, if you provide a password-secret to Weave Net then encryption is enabled. The full documentation for this is on the Weave Net documentation page Changing Configuration Options.

Create a Kubernetes Secret to be used by Weave Net

First you need to create a Kubernetes Secret containing the password you wish to use for Weave Net. For example, you can do this via Bash. Create a weave-secret file with your password:

cat > weave-secret << EOF

Next, call Kubernetes to create a Secret named weave-secret:

kubectl create secret -n kube-system generic weave-secret --from-file=./weave-secret

Now we can deploy or update Weave Net to use that secret.

Deploy Weave Net with encryption enabled

The following command will deploy Weave Net to your Kubernetes cluster with encryption enabled, or will update your existing Weave Net set-up:

kubectl apply -f "$(kubectl version | base64 | tr -d '\n')&password-secret=weave-secret"

You must wait a couple of minutes for Weave Net to start or restart, and once it is running you should be able to see it running in the kube-system namespace, for example:

$ kubectl get pods -n=kube-system | grep weave
weave-net-dqn8k                                        2/2       Running   0          2h
weave-net-lzxzt                                        2/2       Running   0          2h
weave-net-mhp2g                                        2/2       Running   0          2h

And should be able to see that the password option is set in each Pod via the kubectl describe command, for example:

$ kubectl -n=kube-system describe pods weave-net-dqn8k | grep PASS
      WEAVE_PASSWORD:  <set to the key 'weave-secret' in secret 'weave-secret'>  Optional: false

If you have problems, you may find the Weave Net Troubleshooting page helpful.

Ingress TLS Termination

Ingress TLS Termination should be used to ensure that network communication to the CloudBees Core web interfaces is encrypted from end to end.

If you would like to ensure that web browser to CloudBees Core communications is encrypted end-to-end then you will need to change the Kubernetes Ingress used by CloudBees Core to use your TLS Certificates, thereby making it the termination point for TLS.

This section provides an overview of the changes you’ll need to make, but the definitive guide to setting this up is in the Kubernetes Ingress TLS documentation.

Store your TLS Certs in a Kubernetes Secret

To make your TLS Certs available to Kubernetes, you must create a Kubernetes Secret using the Kubernetes command-line tool kubectl. For example, if your certs are in /etc/mycerts you would issue this command to create a secret named my-certs:

kubectl create secret tls my-certs \
--cert=/etc/mycerts/domain.crt --key=/etc/mycerts/privkey.pem

For more information and options see the definitive guide to secrets in the Kubernetes Secrets documentation.

Change the two CloudBees Core Ingresses to be the TLS termination point

Next, you must configure the CloudBees Core Ingress to use your TLS Certs. You do this by editing the Ingress resource named "cjoc" in the cloudbees-core.yml configuration file, uncommenting the lines around tls: and setting the correct hostname and setting the secretName to the secret that holds your TLS certificates. For example, if your CloudBees Core host name is and your TLS Certs secrets file is named my-certs then this is what the new CloudBees Core resource should look like.

apiVersion: extensions/v1beta1
kind: Ingress
  name: cjoc
  annotations: "nginx" "true"
    # "413 Request Entity Too Large" uploading plugins, increase client_max_body_size 50m "off"
  - hosts:
    secretName: my-certs
  - http:
      - path: /cjoc
          serviceName: cjoc
          servicePort: 80

And make the same change to the Ingress named "default".

Next you need to deploy CloudBees Core or update your existing CloudBees Core deployment to use your new Ingress definition. Either way, you need to run this command:

kubectl create -f cloudbees-core.yml

If CloudBees Core has not been deployed, then that command will deploy it. If CloudBees Core has already been deployed then that command will update the existing configuration.

Configuring Persistent Storage

For persistence of CloudBees Core Operations Center and Managed Master data, CloudBees Core must be able to dynamically provision persistent storage. When deployed, the system will provision storage for CloudBees Core Operations Center’s JENKINS_HOME directory and whenever a new Managed Master is provisioned, CloudBees Core Operations Center will provision storage for that master’s JENKINS_HOME.

On Kubernetes, dynamic provisioning of storage is accomplished by creating a Persistent Volume Claim which will use a Storage Class to coordinate with a storage provisioner to provision that storage and make it available to CloudBees Core.

Please refer to the next section in order to set up a storage class for your environment, if applicable.


A detailed explanation of Kubernetes Storage concepts is beyond the scope of this document. For additional background information, refer to the Kubernetes Dynamic Provisioning and Storage Classes blog post, Persistent Volumes and Storage Classes section of the Kubernetes documentation.

Domain Name Change

  • Stop all Managed Masters/Teams Masters from Operations Center dashboard. This can be achieved either automatically with a cluster operation or manually using Managed Master/Team Master  Manage.

  • Add the new domain name by modifying the hostname in ingress/cjoc and cm/cjoc-configure-jenkins-groovy. There are two ways to do this:

    • By changing those hostname values in the cloudbees-core.yml file.

    • By editing the Operations Center ingress resource and modifying the domain name.

      $ kubectl edit ingress/cjoc

      Modify the Operations Center configuration map to change the cjoc URL.

      $ kubectl edit cm/cjoc-configure-jenkins-groovy
  • Delete the Operations Center pod waiting until is terminated.

    $ kubectl delete pod/cjoc
  • Verify that Operations Center  Manage Jenkins  Configure System  Jenkins Location  Jenkins URL has been properly updated. If it hasn’t, change to the new one and click on Save.

  • Start all Managed Masters/Team Masters from Operations Center dashboard. This can be achieved either automatically with a cluster operation or manually using Managed Master/Team Master  Manage.

The new domain name must appears in all of those resources:

$ kubectl get statefulset/<master> -o=jsonpath='{.spec.template.spec.containers[?("jenkins")].env}'
$ kubectl get cm/cjoc-configure-jenkins-groovy -o json
$ kubectl get ingress -o wide

The domain name must be the same than what is used in the browser otherwise a default backend - 404 will be returned.

Domain Name Change in OpenShift

  • Stop all Managed Masters/Teams Masters from Operations Center dashboard. This can be done either automatically with a cluster operation or manually from Managed Master/Team Master  Manage.

  • Modify the hostname in route/cjoc and cm/cjoc-configure-jenkins-groovy to add the new domain name. Either:

    • Edit the cloudbees-core.yml file to change those hostname values, or

    • Edit the Operations Center route resource to modify the domain name

      $ oc edit route/cjoc

      Edit the Operations Center configuration map and modify the cjoc URL.

      $ oc edit cm/cjoc-configure-jenkins-groovy
  • Delete the Operations Center pod waiting until is terminated.

    $ oc delete pod/cjoc
  • Verify that Operations Center  Manage Jenkins  Configure System  Jenkins Location  Jenkins URL has been properly updated. If it hasn’t, change to the new one and click on Save.

  • Start all Managed Masters/Team Masters from Operations Center dashboard. This can be done either automatically with a cluster operation or manually from Managed Master/Team Master  Manage.

The new domain name must appears in all of those resources:

$ oc get statefulset/<master> -o=jsonpath='{.spec.template.spec.containers[?("jenkins")].env}'
$ oc get cm/cjoc-configure-jenkins-groovy -o json
$ oc get route -o wide

The domain name must be the same than what is used in the browser otherwise a default backend - 404 will be returned.

Storage Requirements

Because pipelines typically read and write many files during execution, CloudBees Core requires high-speed storage. For an on-premise deployment, CloudBees recommends using NFS 4.1.

By default, CloudBees Core will use whatever class is configured to be the Default Storage class. There are two ways you can provide an NFS-based Storage Class for CloudBees Core:

  1. Create a new NFS-based Storage Class and make it the default. This is the easiest because you don’t have to change the CloudBees Core configuration.

  2. Create a new NFS-based Storage Class and then, before you deploy change the CloudBees Core configuration file to use the new storage class that you created.

Setup the NFS-Client Provisioner

To configure your Kubernetes cluster to use NFS you must install and configure the NFS-Client Provisioner from the Kubernetes Incubator’s External Storage project. To do this, follow the installation instructions for the NFS-Client Provisioner.

Once you are done you will have created a new NFS Storage Class for your cluster. In the examples below, will will assume that you named the class managed-nfs-storage.

Verify that by getting the storage classes via kubectl (or oc if you are using OpenShift):

$ kubectl get sc
NAME                   TYPE
gp2 (default)
managed-nfs-storage    nfs-for-openshift

In the above output you can see that there is a new NFS storage, but it is not the default.

Option #1: Set your NFS Storage Class the Default

Now you must configure your new Storage Class to be the default so that CloudBees Core will it to provision storage.

First, you use a patch command to set your new managed-nfs-storage (or whatever you named it) as the default storage class.

$ kubectl patch storageclass managed-nfs-storage -p '{"metadata": {"annotations":{"":"true"}}}'

Next, you set the gp2 class to not be the default:

$ kubectl patch storageclass managed-nfs-storage -p '{"metadata": {"annotations":{"":"true"}}}'

List the storage classes and you should see your new class is the default:

$ kubectl get sc
NAME                           TYPE
managed-nfs-storage (default)  nfs-for-openshift
Option #2: Configure CloudBees core to use your NFS class by name

If you do not want to change the default storage class of your cluster, then you can refer to your NFS Storage Class by name.

When you install CloudBees Core you must tell CloudBees Core Operations Center which NFS Storage Class to use: When you edit the cje.yml file and look for the definition of a StatefulSet named cjoc. At the end of the definition you will see that it includes volumeClaimTemplates. Uncomment the line that starts with storageClassName and replace some-storage-class with the name of the storage class you wish to use. Here’s what that part of the configuration file looks like:

  - metadata:
      name: jenkins-home
      accessModes: [ "ReadWriteOnce" ]
          storage: 20Gi
      # storageClassName: some-storage-class

When you provision new Managed Masters they will use the same Storage Class as does CloudBees Core Operations Center.

Integrating Single Sign-on

Once your CloudBees Core cluster is up and running you can integrate it with a SAML-based single sign-on (SSO) system and configure Role Based Authentication Controls (RBAC). This is done by installing the Jenkins SAML plugin, configuring it to communicate with your IDP and configuring your IDP to communicate with CloudBees Core.

Prerequisites for this task

You will need the following items before you setup SAML based SSO and RBAC:

  • Jenkins SAML Plugin must be installed in CloudBees Core Operations Center

  • A SAML-based Identity Provider (IDP)

  • Service Provider Metadata for your IDP (an XML file provided by your IDP administrator).

  • The SAML Attribute names used by IDP for these fields (ask your IDP administrator):

    • Username

    • Email

    • Group

when you make changes to the security configuration, you may lock yourself out of the system. If this happens you can recover by following the instructions in the CloudBees Knowledge Base article How do I login into Jenkins after I’ve logged myself out.

Steps to Perform

Install the SAML plugin on CloudBees Core Operations Center by:

  • Login to CloudBees Core Operations Center and select Manage Jenkins  Manage Plugins  Available

  • Enter 'SAML' in the search box

  • Click the checkbox to choose the SAML plugin

  • Press the Download now and install after restart button

  • Check the checkbox labeled Restart Jenkins when installation is complete and no jobs are running (You do not need to install the plugin on Managed Masters, just on CloudBees Core Operations Center.)

Enable and configure SAML authentication

Login to CloudBees Core Operations Center and select Manage Jenkins  Configure Global Security.

Click the Enable security checkbox and confirm there is a SAML 2.0 option in the Security Realm setting. If it is not there, then the Jenkins SAML Plugin is not installed and you need to install the SAML plugin.

Read and carefully follow the Jenkins SAML Plugin instructions.

Enter the IDP Metadata (XML data) and specify the attribute names that your IDP uses for username, email and group membership. When you are ready, click Save to store the new security settings.

Export Service Provider Metadata to your IDP

After you save your security settings, CloudBees Core Operations Center will report your Service Provider metadata (XML data). You must copy this data and give it to your IDP administrator, who will add it to the IDP configuration.

You can find the Service Provider metadata by following a link on the Configure Global Security page at the end of the SAML section. The link looks like this:

Service Provider Metadata which may be required to configure your Identity
Provider (based on last saved settings).

Login to CloudBees Core Operations Center

Once your IDP administrator confirms that your IDP Metadata has been added to the IDP, attempt to login via the Login link in CloudBees Core Operations Center.

Setup RBAC

Refer to the "Role-based matrix authorization strategy" help in Manage Jenkins  Configure Global Security to enable Role Based Access Controls (RBAC).