Cluster and storage requirements

Kubernetes cluster and Helm: refer to Supported platforms for CloudBees CD/RO on Kubernetes.
Database instance
- For a production environment installation, refer to Database instance for details.
- For a non-production environment installation, the CloudBees CD/RO Helm chart automatically installs a MariaDB database instance as a built-in database.

Non-production environment

Cluster capacity

The table below specifies the default memory and CPU requested for each CloudBees CD/RO component in a non-production environment.

CloudBees CD/RO component/service	CPU	Memory
CloudBees CD/RO Server	Per replica: 1.5 CPU, Default number of replicas: 1	Per replica: 6 GiB (Memory assigned to CloudBees CD/RO JVM: 4 GiB)
Web Server	0.25 CPU	256 MiB
CloudBees Analytics Server	Per replica: 0.1 CPU, Default number of replicas: 1	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 component/service

CPU

Memory

CloudBees CD/RO Server

Per replica: 1.5 CPU, Default number of replicas: 1

Per replica: 6 GiB (Memory assigned to CloudBees CD/RO JVM: 4 GiB)

Web Server

0.25 CPU

256 MiB

CloudBees Analytics Server

Per replica: 0.1 CPU, Default number of replicas: 1

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)

Storage

Consult the table below for default storage requirements for a non-production environment.

CloudBees CD/RO component/service	Storage type	Storage amount
CloudBees CD/RO Server	ReadWriteOnce	5 GiB
CloudBees Analytics Server	ReadWriteOnce	10 GiB
Repository Server	ReadWriteOnce	10 GiB

CloudBees CD/RO component/service

Storage type

Storage amount

CloudBees CD/RO Server

ReadWriteOnce

5 GiB

CloudBees Analytics Server

ReadWriteOnce

10 GiB

Repository Server

ReadWriteOnce

10 GiB

Production environment

Cluster capacity

For current cluster capacity and sizing specifications, refer to Supported platforms for CloudBees CD/RO on Kubernetes.

Separate database instance

You must configure a separate database for your installation of CloudBees CD/RO before you initiate the installation. For current database server and sizing specifications, refer to Database server specifications.

Database configuration

The database can be installed inside or outside the cluster. Update the database section in the cloudbees-cd-defaults.yaml file that is specified when installing the cloudbees-flow chart. Refer to the Database Values section in Configuration values.

Persistent Storage

CloudBees CD/RO components need varying levels of persistent storage.

Non-shared storage: A disk or file system that cannot be shared between two pods or two nodes. Examples include AWS EBS, GCP Persistent Disk, and Azure Disk.
Shared storage: A disk or file system that can be shared between two pods or two nodes. Examples include AWS EFS, GCP NFS Server, and Azure Filestore.

Consult the table below for storage requirements.

CloudBees CD/RO component/service Storage type Storage amount Mount point

CloudBees CD/RO component/service	Storage type	Storage amount	Mount point
Shared storage
CloudBees CD/RO Server CloudBees CD/RO Agent (bound)	`ReadWriteMany`	5 GiB	`/plugin-data`
Repository Server	`ReadWriteMany`	20 GiB	`/repository-data`
Non-shared storage
CloudBees Analytics Server	`ReadWriteOnce`	Per replica: 4, 10 GiB Default number of replicas: 3	`/elasticsearch-data`
CloudBees CD/RO Agent (worker)	`ReadWriteMany`	5GiB	`/workspace`
Zookeeper			`/var/lib/zookeeper`

Shared storage

CloudBees CD/RO Server

CloudBees CD/RO Agent (bound)

ReadWriteMany

5 GiB

/plugin-data

Repository Server

ReadWriteMany

20 GiB

/repository-data

Non-shared storage

CloudBees Analytics Server

ReadWriteOnce

Per replica: 4, 10 GiB Default number of replicas: 3

/elasticsearch-data

CloudBees CD/RO Agent (worker)

ReadWriteMany

5GiB

/workspace

Zookeeper

/var/lib/zookeeper

CloudBees CD/RO server persistent volume provisioning

Update the storage section in the cloudbees-cd-defaults.yaml file specified when installing the cloudbees-flow chart. Refer to Storage values for details.

CloudBees CD/RO agent persistent volume provisioning

Update the storage section in the cloudbees-cd-agent-defaults.yaml file specified when installing the cloudbees-flow-agent chart. Refer to Storage values for details.

Creating persistent shared storage

Google Cloud Platform or Amazon EKS

To get started, clone the cloudbees-example repo and then use the following instructions.

Google Cloud Platform: Use Filestore to create a fully-managed NFS file server on Google Cloud.

Find information and scripts to provision a Google Cloud Filestore instance in the cloudbees-examples repo.
Amazon EKI: Use Amazon Elastic File System (EFS) to create fully-managed persistent storage.

Find information and scripts to provision an EFS instance in the cloudbees-examples repo.

Red Hat OpenShift

For your convenience, sample code to support persistent volumes and persistent volume claim configuration is available here.

Storage class
- The default storage class used by CloudBees CD/RO must be set to volumeBindingMode: immediate. This is achieved by modifying the yaml file for the existing default storage class or by creating a new, default storage class.
Using Dynamic NFS Client Provisioner with NFS server

Install NFS Client provisioner, if not already installed. Then, use the NFS Client provisioner to dynamically create a persistent volume claim (PVC), as follows.
```
helm repo add stable https://charts.helm.sh/stable
helm repo update
helm install nfs-provisioner stable/nfs-client-provisioner \
--namespace kube-system \
--set nfs.server=<NFS_HOST> \
--set nfs.path=<NFS_PATH>
```
where <NFS_HOST> is the NFS server host, and <NFS_PATH> is the NFS mounted path.

This creates a storage class with the name, nfs-client. Use this storage class during CloudBees CD/RO installation with the following parameters to create PVCs.
- CloudBees CD/RO installations need to set
  --set storage.volumes.serverPlugins.storageClass=nfs-client --set storage.volumes.serverPlugins.storage=10Gi
- Optionally, configure CloudBees CD/RO bound agents to enable the ability to create and mount a PVC by setting:
  --set storage.volumes.boundAgentStorage.enabled=true

Using Existing NFS shared PVC

Create PV using NFS:

oc apply -n <namespace> -f pv.yaml

where pv.yaml is as follows:

## pv.yaml  ###
apiVersion: v1
kind: PersistentVolume
metadata:
  name: flow-server-shared
spec:
  capacity:
    storage: 15Gi
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  storageClassName: nfs-client
  nfs:
    path: <nfs-mount-path>
    server: <nfs-host>

Create PVC manually using NFS:

oc apply -n <namespace> -f pvc.yaml

where pvc.yaml is as follows:

## pvc.yaml ##
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: flow-server-shared
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: nfs-client
  volumeName: flow-server-shared
  resources:
    requests:
      storage: 15Gi

Once you have PV and PVC created in <namespace>, use them during CloudBees CD/RO installations in OpenShift with the setting below.

CloudBees CD/RO installations need to set

--set storage.volumes.serverPlugins.name=my-shared-pvc
--set storage.volumes.serverPlugins.existingClaim=true

Make sure NFS is configured with proper permissions to allow the CloudBees CD/RO server read-write access:

chmod 770 <NFS_PATH>

Additional Red Hat OpenShift requirements

An OpenShift project with permissions to create Role and RoleBinding objects.
A container configured to run in a non-privileged mode. Refer to Custom settings required for Red Hat OpenShift installations for details.

AWS EKS Fargate

AWS Fargate allows you to create a compute engine that allows you to build applications without managing infrastructure. Build web applications, microservices, and APIs using containerized workloads without the need to define server types, or plan and time your application and workload scaling. You can also control your pods using Fargate profiles.

Fargate limitations

There are some limitations to using EKS Fargate as documented in on Amazon’s Fargate introduction. Some limitations to consider when using Fargate with CloudBees CD/RO include:

Privileged containers are not supported on Fargate.
AWS EKS Fargate does not support any other persistent storage than the AWS EFS CSI driver.
MariaDB does not work with EFS as PersistentVolume, so Demo Mode installation is not supported.

Fargate pre-requisites

To use Fargate with CloudBees CD/RO, you must perform the following pre-requisite tasks:

Create an EKS cluster with a Fargate profile.
Follow the steps from AWS Load Balancer Controller to install the AWS Load Balancer controller in the EKS cluster.

Use EKS version 1.19 or later, and AWS Load Balancer Controller 2.2.0 or later is required.
Create a certificate using the AWS Certificate Manager for the required domain name. For example, cloudbees-cd.example.com.
Set up External-DNS. Read the tutorial to set it up on AWS.
Follow the steps from Amazon EFS CSI driver - Amazon EKS to install EFS-CSI and enable efs-sc storage class.
Create static persistent volumes in your EKS Fargate cluster to use in CloudBees CD/RO deployment. Refer to Running stateful workloads with Amazon EKS on AWS Fargate using Amazon EFS.

CloudBees CD/RO needs a minimum of 4 persistent volumes to run in cluster mode, so create 4 static persistent volumes with the correct permissions.

Create an EFS Access point:

aws efs  create-access-point  --file-system-id <EFS_ID> \
     --posix-user "Uid=1000,Gid=1000,SecondaryGids=1000,1000" \
     --root-directory "Path=/<EFS-Mount-PATH>,CreationInfo={OwnerUid=1000,OwnerGid=1000,Permissions=0770}" \
      --output text --query "AccessPointId"

example:

EFS_FS_ACCESS_POINT_ID=$(aws efs  create-access-point  --file-system-id fs-0761c22d156958823 \
     --posix-user "Uid=1000,Gid=1000,SecondaryGids=1000,1000" \
     --root-directory "Path=/cdropv-1,CreationInfo={OwnerUid=1000,OwnerGid=1000,Permissions=0770}" \
      --output text --query "AccessPointId")

echo $EFS_FS_ACCESS_POINT_ID

Create a status persistent volume using the following example template with EFS-File-System-ID and EFS_FS_ACCESS_POINT_ID that were generated from the steps above:

apiVersion: v1
    kind: PersistentVolume
    metadata:
      name: cdropv-1
    spec:
      capacity:
        storage: 10
      volumeMode: Filesystem
      accessModes:
        - ReadWriteMany
      persistentVolumeReclaimPolicy: Retain
      csi:
        driver: efs.csi.aws.com
        volumeHandle: fs-0761c22d156958823::fsap-0a98caadf4a4553f4
        # volumeHandle: <EFS_ID>::<EFS_FS_ACCESS_POINT_ID>

Create 4 static persistent volumes to run CloudBees CD/RO successfully on AWS EKS Fargate.

Configuring CloudBees CD/RO for AWS Fargate

To support Fargate on CloudBees CD/RO you must perform the following steps

Set your platform as EKS in the pv.yaml configuration:

# Configure platfrom as eks to configure alb controller as ingress
platform: eks

Update all storage classes to efs-sc (EFS CSI enabled storage class):

#  persistent storage  configuration
storage:
  volumes:
    serverPlugins:
      name: flow-server-shared
      accessMode: ReadWriteMany
      storageClass: efs-sc
    repositoryStorage:
      storage: 10Gi
      storageClass: efs-sc
      accessMode: ReadWriteMany
    doisStorage:
      storageClass: efs-sc
      accessMode: ReadWriteMany
    boundAgentStorage:
      storageClass: efs-sc
      accessMode: ReadWriteMany

Privileged containers aren’t supported on Fargate, so disable volume permissions:

#---------------------------------------------
# Volume configuration section
#---------------------------------------------
volumePermissions:
  enabled: false

Privileged containers aren’t supported on Fargate, so disable sysctlInitContainer.

Fargate takes time to launch pods, so increase the initial time for liveness and readiness probes:

dois:
  sysctlInitContainer:
    enabled: false
  healthProbeLivenessInitialDelaySeconds: 600
  healthProbeReadinessInitialDelaySeconds: 200

Use EFS CSI storage class with zookeeper and use 1 replica:

#---------------------------------------------
# Zookeeper configuration section
#---------------------------------------------
zookeeper:
  persistence:
    enabled: true
    storageClass: efs-sc
    accessMode: ReadWriteMany
  replicaCount: 1

Disable nginx-ingress for Kubernetes versions 1.21 and earlier. Disable ingress-nginx for Kubernetes versions 1.22 and later. AWS EKS Fargate only supports an ALB Ingress controller:

#---------------------------------------------
# nginx-ingress/ingress-nginx configuration section
# Fargate uses the ALB ingress controller. Disable the nginx-ingress and ingress-nginx controllers.
#---------------------------------------------
nginx-ingress:
  enabled: false

ingress-nginx:
  enabled: false

Configure flow-ingress with ALB ingress controller as mentioned in pre-requisites:

#---------------------------------------------
# Flow ingress configuration section
#---------------------------------------------
ingress:
  enabled: true
  host: cloudbees-cd.example.com
# use alb controller  from pre-requisite section
  class: alb
# use acm certificates  from pre-requisite section
  annotations:
      alb.ingress.kubernetes.io/certificate-arn: "arn:aws:acm:us-east-1:XXXXX:certificate/XXXX"

After configuration, during installation, set timeout to 4000s to allow Fargate to deploy all components:

helm upgrade releaseName cloudbees/cloudbees-flow \
          -f valuesFile --namespace nameSpace --timeout 4000s