For details about supported platforms for CloudBees CI on modern cloud platforms, such as supported Kubernetes, Helm, and NFS versions, refer to Supported platforms for CloudBees CI on modern cloud platforms.
Before installing CloudBees CI on modern cloud platforms, you should install the
cbsupport command-line tool. You can use
cbsupport to collect data commonly required for supporting CloudBees products. You can then send that data to the CloudBees Support team to troubleshoot any issues with your CloudBees CI on modern cloud platforms solution.
For instructions on how to install
cbsupport, refer to the cbsupport CLI documentation.
The following items are required to install CloudBees CI on modern cloud platforms on PKS:
On your local computer or a bastion host:
A Kubernetes client with a currently supported version of Kubernetes, installed and configured (
kubectl). Beta releases are not supported.
TKGI CLI (See Installing the TKGI CLI for instructions).
A TKGI cluster running a currently supported version of Kubernetes. Beta releases are not supported.
Cluster nodes configured with at least 2 CPU and 4 GB of memory.
The cluster must have network access to container images (public Docker Hub or a private Docker Registry).
A namespace in the cluster (provided by your admin) with permissions to create
Kubernetes cluster Default Storage Class defined and ready to use.
Refer to the Reference Architecture for TKGI - Storage Requirements for more information.
Dynamic provisioning is required to create persistent volumes. If you don’t enable dynamic provisioning, you will have to manually create a persistent volume.
Because Jenkins is highly dependent upon the filesystem, the underlying storage provider must provide minimal input/output operations per second (IOPS) and latency.
CloudBees CI on modern cloud platforms requires an Ingress controller and has been tested using the Kubernetes NGINX Ingress Community version. Ingress-nginx is the only supported controller.
CloudBees CI creates one Ingress object for the operations center and one for each controller.
If you use an unsupported Ingress controller, you may need to add additional configurations for domains, hostnames, WebSocket, or TCP pass-through. CloudBees documentation can help you with that, but CloudBees does not support this kind of controller. In this case, you must install and configure your Ingress controller and adjust your CloudBees CI chart values according to your situation.
If you plan to provide High Availability (active/active), the load balancer must be configured to enable sticky sessions or session affinity.