Supported platforms for CloudBees CI on modern cloud platforms

CloudBees supports running CloudBees CI on modern cloud platforms on:

The following criteria are required for the above supported Kubernetes platforms:

CloudBees supports only production releases of Helm: RC, beta, patch or experimental releases of Helm are not supported.

Starting with CloudBees CI on modern cloud platforms version 2.204.3.4, Helm version 3.0.2 or later is supported.

We recommend that you migrate to Helm V3 as soon as possible. Support of Helm V2 was deprecated in July 2020.

As of CloudBees CI on modern cloud platforms version 2.190.3.2, CloudBees CI on modern cloud platforms supports Microsoft Windows containers for Kubernetes 1.x starting with version 1.14. Each cloud provider has various levels of support for Kubernetes features, including Windows containers, so confirm the status with your cloud platform provider.

As of CloudBees CI on modern cloud platforms version 2.263.4.1, Microsoft Windows LTSC 2019 (version 1809) is supported for agents running on Google Kubernetes Engine (GKE) clusters, but not for the Operations Center or controllers. If running Windows workloads with agents on a GKE cluster, the image provided by CloudBees CI on modern cloud platforms only works on version 1809 of Windows LTSC.

This feature is documented in Managing agents - Running CloudBees CI build agents in Windows containers.

CloudBees supports the following versions of NFS:

CloudBees supports Amazon EFS as a storage backend for CloudBees CI. However, like any technology, Amazon EFS comes with tradeoffs that should be explored and understood.

You can use EFS to create a volume available across multiple Availability Zones. However, this comes at the cost of both performance and a higher price. Due to EFS’s nature, it will almost always perform slower than EBS, which some will find unacceptable. For fine-tuning the EFS performance configuration, please refer to Amazon’s documentation: https://aws.amazon.com/premiumsupport/knowledge-center/linux-efs-performance-modes/.

Although rare, customers have encountered issues with the default settings (Burst Credits), resulting in a complete outage of the platform.

If you open a support case about a problem with CloudBees CI on Amazon EFS, we will work with you to ensure that the CloudBees CI product is working correctly. If we believe that the problem is due to the performance of Amazon EFS, we may ask you to open a support case with Amazon to resolve the issue. In some rare situations, the CloudBees CI product may be working as intended, and the CloudBees support ticket may be closed without resolution of the reported problem.

High Availability (HA) on a Windows environment is not supported.

Configuration as Code (CasC) for Masters is supported in CloudBees CI on modern cloud platforms as of May 2020.

The following plugins support Configuration as Code (CasC).

If you don’t see a plugin in this list, this can mean one of two things: that plugin does not support CasC or that plugin does not require configuration.

This list of plugins applies to CloudBees CI, CloudBees Jenkins Distribution, and CloudBees Jenkins Platform.