Supported platform information for CloudBees CD/RO deployments on Kubernetes.
Looking for information about CloudBees CD/RO on traditional platforms? Refer to Supported platforms for CloudBees CD/RO on traditional platforms.
Supported container services
| Kubernetes container service | 9.2 | 10.0 | 10.1 | 10.2 | 10.3 |
|---|---|---|---|---|---|
AKS 1.21.x | |||||
AKS 1.20.x | |||||
AKS 1.19.x | |||||
AKS 1.18.14 | |||||
AKS 1.17.16 | |||||
Amazon EKS 1.21.x | |||||
Amazon EKS 1.20.x | |||||
Amazon EKS 1.19.x | |||||
Amazon EKS 1.18.9 | |||||
Amazon EKS 1.17.12 | |||||
Amazon EKS 1.16.15 | |||||
GKE 1.21.x | |||||
GKE 1.20.x | |||||
GKE 1.19.x | |||||
GKE 1.18.x | |||||
GKE 1.17.x | |||||
GKE 1.16.x | |||||
OpenShift 4.5.x |
| Helm | 9.2 | 10.0 | 10.1 | 10.2 | 10.3 |
|---|---|---|---|---|---|
Helm 3, version 3.1.0 or later |
-
CloudBees supports only production releases of Helm: RC, beta, patch or experimental releases of Helm are not supported.
Supported databases
| Platform | 9.0 | 9.1 | 9.2 | 10.0 | 10.1 | 10.2 | 10.3 |
|---|---|---|---|---|---|---|---|
MySQL 8.0 1 | |||||||
MySQL 5.7 or later 1 | |||||||
MS SQL Server 2019 | |||||||
MS SQL Server 2017 | |||||||
MS SQL Server 2016 | |||||||
MS SQL Server 2014 | 2 | 2 | 2 | 2 | 2 | ||
MS SQL Server 2012 R4 | 2 | 2 | 2 | 2 | 2 | ||
Oracle 19c | |||||||
Oracle 18c | |||||||
Oracle 12c | |||||||
MariaDB 3 |
1 Clean installations of the CloudBees CD/RO server require the MySQL JDBC driver. For upgrades, additions to my.cnf/my.ini are required. See Installing the MySQL JDBC Driver.
2 As of version 9.2, CloudBees CD/RO has ended support for HTTPS connection types older than TLS 1.2. If you are using MS SQL Server 2012 or 2014, you must update it to support TLS1.2. For details, see the Microsoft TLS 1.2 support for Microsoft SQL Server web page.
3 The built-in MariaDB database is a supported database for production use with CloudBees Analytics for CloudBees CI, only. It continues to not be supported for production use for CloudBees CD/RO and full CloudBees Software Delivery Automation.
Supported browsers
CloudBees CD/RO supports the following web browsers:
-
Microsoft Internet Explorer 11
-
Microsoft Edge
-
Mozilla Firefox
-
Google Chrome
| Web browser extensions such as AdBlock Plus for Google Chrome can interfere with the display of CloudBees CD/RO web pages. You should disable any ad-blocking browser extensions or add an exclusion for CloudBees CD/RO web pages. |
Kubernetes cluster requirements
The table below specifies the default memory and CPU requested for each CloudBees CD/RO component in the production environment per deployment size.
Small to mid-range deployments
A small to mid-range deployment is defined as:
-
<1K jobs per day
-
<100 running pipelines per day
-
< 50K job steps
| CloudBees CD/RO component/service | CPU | Memory |
|---|---|---|
CloudBees CD/RO Server | Per replica: 2 CPU, Default number of replicas: 1 | Per replica (minimum): 16 GiB (Memory assigned to CloudBees CD/RO JVM: 85%) Per replica (recommended): 32 GiB (Memory assigned to CloudBees CD/RO JVM: 30 GiB) Local storage per replica: 20 GB |
Web Server | 0.25 CPU | 256 MiB |
CloudBees Analytics Server | Per replica: 0.1 CPU, Default number of replicas: 3 | Per replica: 2 GiB (Memory assigned to Elasticsearch JVM: 1 GiB) |
Repository Server | 0.25 CPU | 512 MiB (Memory assigned to Repository JVM: 512 MiB) |
CloudBees CD/RO Agent (Bound) | 0.25 CPU | 512 MiB (Memory assigned to Agent JVM: 256 MiB) |
CloudBees CD/RO Agent (Worker) | 0.25 CPU | 512 MiB (Memory assigned to Agent JVM: 64 MiB) |
ZooKeeper | Per replica: 0.25 CPU, Default number of replicas: 3 | Per replica: 1 GiB |
Very large deployments
A very large deployment is defined as:
-
~ 100K jobs per day
-
~ 2000 running pipelines per day
-
~ 5M job steps per day
| CloudBees CD/RO component/service | Instance CPU | Instance Memory | Max JVM heap | Local storage | Replicas |
|---|---|---|---|---|---|
CloudBees CD/RO server | 16 | 128 GiB | 85% | 60 GiB | 3 |
CloudBees CD/RO agent | 1 | 1 GiB | 64 MiB | 5 GiB | 2 |
Web server | 1 | 512 GiB | n/a | n/a | 2 |
Analytics server | 4 | 16 GiB | n/a | 20 GiB | 3 |
Repository server | 0.25 | 1 GiB | 512 MiB | 20 GiB | 1 |
CloudBees CD/RO bound agent | 0.25 | 1 GiB | 256 MiB | n/a | 1 |
Zookeeper | 0.25 | 512 GiB | n/a | n/a | 3 |
CloudBees CD/RO server requirements
| Small to mid-range deployments | Large deployments | Very large deployments | CloudBees Analytics for CloudBees CI |
|---|---|---|---|
|
|
| Not applicable. |
CloudBees CD/RO Server hardware specifications | |||
Processor (CPU) per instance: 2 CPU’s Default number of replicas: 1 | Processor (CPU) per instance: 4 CPU’s Default number of replicas: 3 | Processor (CPU) per instance: 16 CPU’s Default number of replicas: 3 | Processor (CPU) per instance: 4 core processors per instance |
Available RAM per replica: 16 GB (minimum) 32 GB (recommended) Max JVM Heap size: 85%* | Available RAM per replica: 32 GB (minimum) 64 GB (recommended) Max JVM Heap size: 85%* | Available RAM per replica: 64 GB (minimum) 128 GB (recommended) Max JVM Heap size: 85%* | Available RAM per replica: 8 GB (minimum) 16 GB (recommended) Max JVM Heap size: 40%* |
Local storage per replica: 20 GB | Local storage per replica: 40 GB | Local storage per replica: 60 GB | Local storage per replica: 10-20 GB (learn more here) |
Instances in cluster: 1 for non-clustered 2-3 recommended for HA | Instances in cluster: 3 instances | Instances in cluster: 3 or more instances | Instances in cluster: 1 for non-clustered 3 recommended for HA (MariaDB is not supported in a clustered deployment.) |
*The maximum JVM heap size specified in wrapper.conf, expressed in percentage of total available memory.
CloudBees Analytics server requirements
| Small to mid-range deployments | Large deployments | Very large deployments | CloudBees Analytics for CloudBees CI |
|---|---|---|---|
|
|
|
|
Processor (CPU) per instance: 4 core processor | Processor (CPU) per instance: 4 core processor | Processor (CPU) per instance: 8 core processor | Processor (CPU) per instance: 1 core processor |
Available RAM per instance: 4 GB (minimum) 8 GB (recommended) JVM Heap size for Elasticsearch: 2 GB (minimum) 4 GB (recommended) JVM Heap size for Logstash: 1 GB (minimum) 2 GB (recommended) | Available RAM per instance: 8 GB (minimum) 16 GB (recommended) JVM Heap size for Elasticsearch: 4 GB (minimum) 8 GB (recommended) JVM Heap size for Logstash: 2 GB (minimum) 4 GB (recommended) | Available RAM per instance: 8 GB (minimum) 16 GB (recommended) JVM Heap size for Elasticsearch: 4 GB (minimum) 8 GB (recommended) JVM Heap size for Logstash: 2 GB (minimum) 4 GB (recommended) | Available RAM per instance: 3 GB (minimum) JVM Heap size for Elasticsearch: 1 GB (minimum) JVM Heap size for Logstash: 512 GB (minimum) |
Disk Space: 5 GB | Disk Space: 10 GB | Disk Space: 20 GB | Disk Space: 10 GB |
Instances in cluster: 1 (non-clustered) 2-3 (recommended for HA) | Instances in cluster: 3 instances | Instances in cluster: 3 or more instances | Instances in cluster: 1 (non-clustered) 3 (recommended for HA) |
*The maximum JVM heap size specified in wrapper.conf, expressed in percentage of total available memory.
Database server requirements
| Small to mid-range deployments | Large deployments | Very large deployments |
|---|---|---|
|
|
|
Recommended database: Any supported database type - Mysql, MS SQL Server, Oracle | Recommended database: Oracle or MS SQL Server | Recommended database: Oracle or MS SQL Server |
Processor (CPU): 4 core processor | Processor (CPU): 8 core processor | Processor (CPU): 16 core processor |
Available RAM: 16 GB | Available RAM: 20 GB or more | Available RAM: 20 GB or more |
CloudBees CD/RO Agent requirements
| Not applicable for CloudBees Analytics for CloudBees CI installations. |
-
Processor (CPU) per instance: 1 CPU processor from set of cores
-
JVM heap size per stand-alone agent: 16 MiB (minimum), 64 MiB (recommended)
-
JVM heap size when shared with other CloudBees CD/RO components: 256 MiB (minimum), 512 MiB (recommended)
-
Disk Space: 5 GB