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.
The following items are required to install CloudBees CI on modern cloud platforms on Kubernetes:
A Kubernetes client with the currently supported version of Kubernetes, installed and configured on your local computer or a bastion host. Beta releases are not supported.
A cluster running a currently supported version of Kubernetes. Beta releases are not supported.
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 Role and RoleBinding objects.
Kubernetes cluster Default Storage Class defined and ready to use.
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 creates one Ingress object for the operations center and one for each controller. If you do not use subdomains, the operations center and controllers share the same hostname by default. Therefore, you must use an Ingress controller that supports multiple Ingresses using the same hostname.
Inbound agents use WebSockets to connect to controllers, so the Ingress controller and the corresponding load balancer should support WebSockets.
If you use TCP to connect to inbound agents, the only supported Ingress Controller is NGINX Ingress Controller.
If you use the NGINX Ingress Controller, an
IngressClass object is required.
The CloudBees CI on modern cloud platforms installation will fail without one.
For more information, refer to What is an IngressClass and why is it important for users of Ingress NGINX Controller now?