Refer to the following sections for requirements and recommendations:
Not all combinations of server version and agent version are supported. This is because of an ectool/Perl API communication incompatibility as well as a Diffie-Hellman key size incompatibility.
CloudBees CD/RO server requirements on Kubernetes
CloudBees recommends the following guidelines for servers in a Kubernetes installation, based on deployment size.
| The following guidelines are a recommended starting point. You may need to scale up, based on your environment and needs. |
| 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 CPUs Default number of replicas: 1 |
Processor (CPU) per instance: 4 CPUs Default number of replicas: 3 |
Processor (CPU) per instance: 16 CPUs Default number of replicas: 3 |
Processor (CPU) per instance: 4 core processors |
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 high availability (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 CD/RO server requirements for traditional installations
CloudBees recommends the following guidelines for servers in a traditional installation, based on deployment size.
| The following guidelines are a recommended starting point. You may need to scale up, based on your environment and needs. |
| 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: 4 core processor |
Processor (CPU) per instance: 8 core processor |
Processor (CPU) per instance: 16 core processor |
Processor (CPU) per instance: 4 core processor |
Available RAM per instance: 16 GB (minimum) 64 GB (recommended) Max JVM Heap size: 40%* |
Available RAM per instance: 64 GB (minimum) 128 GB (recommended) Max JVM Heap size: 60%* |
Available RAM per instance: 64 GB (minimum) 256 GB (recommended) Max JVM Heap size: 70%* |
Available RAM per instance: 8 GB (minimum) 16 GB (recommended) Max JVM Heap size: 40%* |
Disk Space: 20 GB |
Disk Space: 30 GB or more |
Disk Space: 50 GB or more |
Disk Space: 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-4 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 CD/RO agent requirements
These requirements are applicable to both traditional and Kubernetes installations.
| These requirements are 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
ZooKeeper requirements
ZooKeeper is a centralized service used in CloudBees CD/RO to store configuration data and synchronize group services. Your clients must be compatible with the CloudBees CD/RO ZooKeeper server version. CloudBees CD/RO currently uses ZooKeeper v3.8.4.
|
The following requirements apply to CloudBees CD/RO versions:
-
CloudBees CD/RO v2024.06.0 and later uses v3.8.4. Your platform must be compatible with ZooKeeper server v3.8.4.
-
CloudBees CD/RO v2023.12.0 to v2024.03.0 uses v3.8.3. Your platform must be compatible with ZooKeeper server v3.8.3.
-
CloudBees CD/RO server v10.5.0 to v2023.10.0 is only compatible with ZooKeeper server v3.8.0.
| ZooKeeper has specific OS limitations and JDK version requirements. For more information, refer to Apache ZooKeeper. |
Diffie-Hellman key size requirement
To enable the CloudBees CD/RO server version 10.0 and later to configure Diffie-Hellman cipher suites properly, agent versions 10.0 or later can only connect to external applications that require SSL with a minimum key size of 2048 bits.
|
Diffie-Hellman key size requirement for legacy CloudBees CD/RO versions
To enable the CloudBees CD/RO server versions 7.0 - 9.2 to configure Diffie-Hellman cipher suites properly, CloudBees CD/RO uses OpenSSL-1.0.1T or newer versions with SSLv2 enabled. Because of OpenSSL and JRE changes, the minimum Diffie-Hellman key size requirement is increased to 1024 bits (from 768 bits) as of version 7.0. Server versions 7.0 or newer use Jetty (a Java HTTP server), which listens on the 8000 (unsecure) and 8443 (secure) ports. Server versions 7.0 or newer use Java 1.8.0_66, in which the ephemeral DH key size defaults to 1024 bits during SSL/TLS handshaking in the SunJSSE provider. For details on the increase of the key size requirement as of Java 1.6-u101, refer to the Java 6u101 b31 release notes. For details as of Java 1.7-u85, refer to the Java 7u79 release notes. Because their minimum key size is 1024 bits, agent versions 7.0 or newer can connect only to:
However, CloudBees CD/RO Automation Platform agents of versions 5.0.6, 5.3, or 5.4 and CloudBees CD/RO agent versions 6.0.1 or 6.5 or newer can connect to all CloudBees CD/RO server versions (including 7.0 or newer) via ectool and ec-perl. CloudBees CD/RO Automation Platform server versions 5.0.6 or 5.3 or newer can run jobs using all agent versions (including 7.0 or newer). CloudBees CD/RO server versions 7.0 or newer can run jobs using CloudBees CD/RO Automation Platform agent versions 5.0.6 or 5.3 or newer. |