When running CloudBees CI on modern cloud platforms, consult this page for supported platforms.
Kubernetes
CloudBees supports running CloudBees CI on modern cloud platforms on the following Kubernetes platforms.
Kubernetes version | 1.20 | 1.21 | 1.22 | 1.23 | 1.24 |
---|---|---|---|---|---|
CloudBees CI on modern cloud platforms 2.303.x |
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.319.x |
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.332.x |
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.346.x |
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.361.x |
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.375.x |
|
|
|
|
|
CloudBees supports the following Kubernetes distribution providers:
-
Azure Kubernetes Service (AKS)
-
Amazon Elastic Kubernetes Service (EKS) versions 1.21 through 1.24
-
Google Kubernetes Engine (GKE) versions 1.22+
-
VMware Tanzu Kubernetes Grid Integrated Edition (TKGI)
-
CNCF-certified Kubernetes Platform Certified Kubernetes Distribution or Platform Certified Kubernetes Hosted, cluster versions 1.20 through 1.24.
The following criteria are required for the above supported Kubernetes platforms:
-
The version is Generally Available.
CloudBees does not support or recommend "proof of concept" offerings of Kubernetes platforms or Beta or Public preview versions.
-
The version is actively supported by the Kubernetes distribution provider.
Sidecar injector requirements on Kubernetes
Sidecar injector version 2.3.2 requires Kubernetes version 1.21 or later. If you run an earlier supported version of Kubernetes, install sidecar injector version 2.1.3. When performing a Helm installation, the latest version of the sidecar-injector is installed by default.
Red Hat OpenShift Container Platform (OCP)
CloudBees supports running CloudBees CI on modern cloud platforms on following versions of OCP.
OCP version | OCP 4.6 | OCP 4.7 | OCP 4.8 | OCP 4.9 | OCP 4.10 | OCP 4.11 |
---|---|---|---|---|---|---|
CloudBees CI on modern cloud platforms 2.303.x |
|
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.319.x |
|
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.332.x |
|
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.346.x |
|
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.361.x |
|
|
|
|
|
|
CloudBees CI on modern cloud platforms 2.375.x |
|
|
|
|
|
|
Supported Helm
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.346.2.2, Helm version 3.5.0 or later is supported.
For CloudBees CI on modern cloud platforms versions from 2.204.3.4 until 2.346.1.4, Helm version 3.0.2 or later is supported.
Refer to the Helm Version Support Policy for information about version skew between the Helm version and your Kubernetes version. |
We recommend that you migrate to Helm V3 as soon as possible. Support of Helm V2 was deprecated in July 2020.
Microsoft Windows containers
CloudBees CI on modern cloud platforms supports using Microsoft Windows containers for Kubernetes, however you can only run CloudBees CI on modern cloud platforms agents in Windows containers. Running controllers or the operations center on Microsoft Windows containers in Kubernetes is not supported. Each cloud provider has various levels of support for Kubernetes features, including Windows containers, so confirm the status with your cloud platform provider.
The following versions of CloudBees CI on modern cloud platforms support running agents in Windows 10 (version 1809)/Windows Server 2019 containers:
-
CloudBees CI on modern cloud platforms 2.277.x
-
CloudBees CI on modern cloud platforms 2.289.x
-
CloudBees CI on modern cloud platforms 2.303.x
-
CloudBees CI on modern cloud platforms 2.319.x
-
CloudBees CI on modern cloud platforms 2.332.x
-
CloudBees CI on modern cloud platforms 2.346.x
-
CloudBees CI on modern cloud platforms 2.361.x
-
CloudBees CI on modern cloud platforms 2.375.x
This feature is documented in Managing agents - Running CloudBees CI build agents in Windows containers.
ARM64
CloudBees distributes Docker container images for ARM64 architecture for CloudBees CI on modern cloud platforms.
NFS
CloudBees supports the following versions of NFS:
-
NFS v.3.x
-
NFS v4.1 and higher
There are known performance issues with NFS v4.0. CloudBees supports NFS v4.1 and higher, but CloudBees does not support NFS v4.0. |
Amazon Elastic File System (Amazon EFS)
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.
Configuration as Code (CasC) for Controllers
Configuration as Code (CasC) for Controllers is supported in CloudBees CI on modern cloud platforms as of May 2020.
|
Tier 1 and Tier 2 plugins support for Configuration as Code
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.
Plugin Name | Minimum version | Configuration example |
---|---|---|
active-directory |
2.16 |
|
ant |
1.10 |
|
antisamy-markup-formatter |
1.6 |
|
artifact-manager-s3 |
1.1 |
|
aws-credentials |
1.28 |
|
aws-global-configuration |
1.4 |
|
cloudbees-assurance |
2.138.0.13 |
|
cloudbees-bitbucket-branch-source |
2.4.0 |
|
cloudbees-cloudfoundry-cli |
2.1.6 |
|
cloudbees-cyberark-credentials |
1.0.5 |
|
cloudbees-jenkins-advisor |
3.0 |
|
cloudbees-monitoring |
2.9 |
|
cloudbees-nodes-plus |
1.20 |
|
cloudbees-plugin-usage |
2.7 |
|
cloudbees-request-filter |
1.7 |
|
cloudbees-ssh-slaves |
2.7 |
|
config-file-provider |
3.4 |
https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/config-file-provider |
credentials |
2.2.0 |
https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/credentials |
docker-commons |
1.17 |
|
docker-workflow |
1.23 |
|
dockerhub-notification |
2.5.0 |
|
electricflow |
1.1.14 |
|
git |
3.10.1 |
https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/git |
github-branch-source |
2.5.8 |
|
github |
1.29.5 |
|
google-compute-engine |
4.3.0 |
|
google-oauth |
1.0.2 |
|
gradle |
1.30 |
|
jdk-tool |
1.4 |
|
kube-agent-management |
1.1.32 |
|
kubernetes |
1.25.3 |
|
kubernetes-credentials |
0.7.0 |
|
ldap |
1.16 |
https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/ldap |
mailer |
1.25 |
https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/mailer |
master-provisioning-kubernetes |
2.5.1 |
|
matrix-auth |
2.4 |
|
maven |
3.7 |
|
metrics |
4.0.2.4 |
|
nodejs |
1.3.6 |
|
notification-api |
1.2 |
|
pam-auth |
1.6 |
https://github.com/jenkinsci/pam-auth-plugin/blob/master/src/test/resources/config.yaml |
plain-credentials |
1.5 |
|
saml |
1.1.3 |
https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/saml |
script-security |
1.64 |
|
secure-requester-whitelist |
1.4 |
|
skip-plugin |
4.6 |
|
ssh-credentials |
1.17 |
|
ssh-slaves |
1.30.0 |
|
support-core |
2.68 |
|
trigger-restrictions |
1.3 |
|
timestamper |
1.11.4 |
JDK
CloudBees CI on modern cloud platforms controllers run in a set of Docker containers that come pre-configured with OpenJDK 11. CloudBees does not support the modification of these containers.
If you build your own container images for agents, CloudBees recommends using only JDKs or JREs provided by either Oracle or OpenJDK for only the following versions:
-
Oracle JDK 11 - 64 bits
-
OpenJDK JDK 11 - 64 bits
-
Oracle JRE / JDK 8 - 64 bits 1
-
OpenJDK JDK / JRE 8 - 64 bits 1
1 Support for Java 11 was added in version 2.332.1.4. CloudBees strongly recommends that you upgrade your CloudBees CI instance to Java 11 as soon as possible for the best experience. In a future release, support for Java 8 will be discontinued and you will be unable to run new versions of the product on Java 8 going forward. Releases that occurred during the support window for Java 8 will continue to run on Java 8. |
CloudBees Support may ask you to move forward to a specific update release (for example, _uXX ) of a currently supported JDK/JRE version before diagnosing your problem. If you are running an outdated version of a supported JDK, CloudBees Support may ask you to move to a more recent JDK version since the more recent version may benefit from bug fixes and performance improvements. CloudBees recommends you keep your JDK version up-to-date.
|
Version skew between the operations center and controllers
CloudBees supports managed controllers that run the same version as the operations center or any earlier version that was supported when that version of the operations center was released.
As an example, when CloudBees CI on modern cloud platforms 2.346.1.4 was released, versions 2.277.4.4 through 2.346.1.4 were supported. CloudBees supports connecting any controller within that range to a version 2.346.1.4 operations center. For more information about the support lifecycle, refer to CloudBees maintenance lifecycle policies.
Upgrading between versions
CloudBees supports upgrading CloudBees CI to a version up to one year later than your current version.
As an example, if you are running CloudBees CI on modern cloud platforms 2.263.4.2 which was released on February 26, 2021, you should first upgrade both your operations center and any controllers to a version up to one year later, such as CloudBees CI on modern cloud platforms 2.319.3.4, which was released on February 15, 2022. When that upgrade is successful, you can upgrade again to a version up to one year later.
CloudBees support can help you plan and prepare for your upgrade, for more information, refer to Required Data: Assisted Update.