Skip to main content
Skip table of contents

Hardware sizing (to be deleted)

Requirements for a Worker HA deployment

Nodes / VMs

vCPU

vRAM

vDisk (GiB)

Comments

CP

Control Plane

2

4

50

See RKE2 installation requirements for hardware sizing, the underlying operating system, and the networking requirements.

CX-A

CX workload

2

4

250

The worker node to schedule workload of CX services that can handle the workload of up to 100 concurrent agents or 300 concurrent conversations.

CX-B

CX workload

2

4

250

Report

Report workload

4

8

250

This for Apache Superset. This workload may also be shared with other worker nodes (CX-A or CX-B).

ETL

ETL services

2

4

250

Expertflow ETL consisting of Apache AirFlow services. This workload may also be shared with other worker nodes (CX-A or CX-B).

Requirements for CX HA deployment

Nodes / VMs

vCPU

vRAM

vDisk (GiB)

Comments

CX A

Control Plane + CX Core + Channels + StatefulSets

4

8

250

This setup assumes three digital channels. Hardware requirements will increase with each additional channel, requiring approximately 0.5 CPU and 1 GB RAM per channel.

CX B

Control Plane + CX Core + Channels + StatefulSets

4

8

250

This setup assumes three digital channels. Hardware requirements will increase with each additional channel, requiring approximately 0.5 CPU and 0.5 GB RAM per channel.

DiChannels

Arbiter

Control Plane + Arbiter

2

4

10

The arbiter node ensures quorum during failover scenarios but does not store data or handle traffic

Reporting

Control Plane + Reporting + ETL

8

16

250

This for Apache Superset and expert flow ETL. HA is not supported for reporting.

Voice

Media Server

8

16

150

HA is not supported for voice.

Requirements for a CX Media Server Standalone deployment

Item

Minimum

Recommended

RAM

512MB

1GB+

Disk space

10GB

20GB+

CPU

Single core 2266 MHz

Dual core 2266 MHz+

Requirements for a CX Switch HA deployment

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.