Prerequisite software and third-party dependencies required for the Genesys Engage cloud private edition environment.
This article describes the prerequisites and third-party infrastructure services (dependencies) you need to deploy before deploying Genesys Engage services.
- Domain Name System (DNS)
- Helm 3.0+
- Ingress Controller
- JFrog Edge Artifactory account
- Kubernetes 1.18.x - 1.19.x
- Session Border Controller (SBC)
- Web Application Firewall (WAF) - optional, but recommended.
See the table below for details about the prerequisite third party dependencies. Genesys has tested the OpenShift Operators, but you can use any compatible version of these services.
|Name||Version||OpenShift Operator Hub||OpenShift Operator URL||Purpose|
|A container image registry and Helm chart repository||N/A||N/A||N/A||You can use any Docker OCI compliant registry.|
|An SMTP relay||N/A||N/A||N/A||Genesys recommends PostFix, but you can use any SMTP relay that supports standard mail libraries.|
|Kafka||2.x||Banzai Cloud Kafka Operator||https://operatorhub.io/operator/banzaicloud-kafka-operator||Message bus.|
|Keda||2.0||KEDA Operator||https://operatorhub.io/operator/keda||Custom metrics for scaling.|
|Redis||6.x||Redis Enterprise Operator||https://operatorhub.io/operator/redis-enterprise||Used for caching.|
|Consul||1.9.5||N/A||N/A||Service discovery, service mesh, and key/value store.|
|Elasticsearch||7.x||Elasticsearch (ECK) Operator||https://operatorhub.io/operator/elastic-cloud-eck||Used for text searching and indexing.|
|MS SQL Server||2016||N/A||N/A||Relational database.|
OpenShift controls the pod permissions (including user access) through a security feature called security context constraints (SCCs). Genesys has created a customized SCC called genesys-restricted SCC which covers the user access as one of the constraints. See OpenShift security settings for a detailed procedure.
- If you are a Cluster Administrator, you must create a cluster role, create a user group called genesys-restricted-group, assign the cluster role to the user group, and then add users to the group. These users have appropriate permissions to manage Genesys Engage services.
- If you are deploying Genesys Engage services, make sure your user ID is part of the genesys-restricted-group group. Contact your Cluster Administrator to set this for you.