Software requirements

From Genesys Documentation
Jump to: navigation, search

Prerequisite software and third-party dependencies required for the Genesys Engage cloud private edition environment.

Early Adopter Program
Genesys Engage cloud private edition is being released to pre-approved customers as part of the Early Adopter Program. Please note that the documentation and the product are subject to change. For more details about the program, please contact your Genesys representative.

Prerequisites

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.

Third-party dependencies

Genesys Engage services require specific third-party backend services as an infrastructure prerequisite. You can install these third-party infrastructure prerequisites in a different namespace or outside of the cluster provided the namespace has direct network access to these services.
Important
Deploying and maintaining the third party dependencies is your responsibility. Review Understanding responsibilities for more information on your responsibilities and how Genesys supports the deployment process.

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.
Postgres 11.x N/A N/A Relational database.

Permissions

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.