The table below outlines all prerequisites for a CX Contact deployment using Kubernetes.
|Component||Description||Mandatory or Optional|
|CDP NG Access Credentials||As of CX Contact 9.0.025, Compliance Data Provider Next Generation is used as a CDP by default. CDP NG access credentials (ID and Secret) should be obtained before attempting to connect to CDP NG. Request credentials from Genesys Customer Care.||Mandatory|
|Docker||Docker 17.03.2-ce, with CX Contact Docker images stored in the Docker registry.||Mandatory|
|Chrome||The latest version of Chrome must be used as the UI browser.||Mandatory|
|Container orchestration||Any certified K8s platform||Mandatory|
|Network/DNS||All VMs running CX Contact components should belong to the same local network segment and be interconnected so that all components can communicate over the network. DNS must be present in the network and allow for names resolution. CX Contact components always use FQDNs (not IP addresses) to establish communication to each other.||Mandatory|
|Load Balancers||F5 or functionally comparable hardware or software load balancer.
Note: Load balancer must be configured to ensure that internal CX Contact components cannot be accessed via load balancer. Only API Aggregator should be accessible.
|Shared file system (NFS)||NFS||Mandatory|
|Redis||Redis 5.x cluster, Enterprise Redis with persistence is recommended||Mandatory|
|Elasticsearch||ES Cluster 6.3x||Mandatory|
|SFTP Server||Use when automation capabilities are required||Optional|
|Genesys Web Services (GWS)||v.9.0
Note: You will need to push these images to the local Docker registry.
|Mandatory (Deployed using Docker Compose)|
|Genesys core components||v.8.5 or v.8.1
CX Contact components operate with Genesys core services on the back end. It's expected that all voice-processing components (Voice VM and shared services such as GVP) are deployed and running. CX Contact requires a multi tenant Configuration Server.