Before you begin

Find out what to do before deploying Designer.

Related documentation:

• Suite-level guide
• All services
• Designer Release Notes

RSS:

• For private edition

Limitations and assumptions

Designer currently supports multi-tenancy provided by the tenant Configuration Server. That is, each tenant should have a dedicated Configuration Server, and Designer can be shared across the multiple tenants.

Before you begin:

1. Install Kubernetes. Refer to the Kubernetes documentation site for installation instructions. You can also refer to the Genesys Docker Deployment Guide for information on Kubernetes and High Availability.
2. Install Helm according to the instructions outlined in the Helm documentation site.

After you complete the above mandatory procedures, return to this document to complete deployment of Designer and DAS as a service in a K8s cluster.

Download the Helm charts

You will have to download the following Designer related Docker containers and Helm charts from the JFrog repository:

• Docker containers
  • designer/designer:9.0.118.05.5
  • designer/das: 9.0.111.09.14
• Helm charts
  • designer-9.0.118.tgz
  • designer-das-9.0.111.tgz

For more information on JFrog, refer to the Downloading your Genesys Multicloud CX containers topic in the Setting up Genesys Engage cloud private edition document.

Third-party prerequisites

Mandatory prerequisites

• Kubernetes 1.12+
• Helm 3.0
• Docker
  • To store Designer and DAS docker images to the local docker registry.
• Ingress Controller
  • If Designer and DAS are accessed from outside of a K8s cluster, it is recommended to deploy/configure an ingress controller (for example, NGINX), if not already available. Also, the Blue-Green deployment strategy works based on the ingress rules.
  • The Designer UI requires Session Stickiness. Configure session stickiness in the annotations parameter in the values.yaml file during Designer installation.

Optional prerequisites

• Elasticsearch 7.8.0
  • Elasticsearch is used for Designer Analytics and audit trail.
• Redis 3.2.x
  • Redis is used for resource index caching and multi-user collaboration locks on Designer resources.

Storage requirements

The following storage requirements are mandatory prerequisites:

• Persistent Volumes (PVs)
  • Create persistent volumes for workspace storage (5 GB minimum) and logs (5 GB minimum)
  • Set the access mode for these volumes to ReadWriteMany.
  • The Designer manifest package includes a sample YAML file to create Persistent Volumes required for Designer and DAS.
  • Persistent volumes must be shared across multiple K8s nodes. Genesys recommends using NFS to create Persistent Volumes.
• Shared file System - NFS
  • For production, deploy the NFS server as highly available (HA) to avoid single points of failure. It is also recommended that the NFS storage be deployed as a Disaster Recovery (DR) topology to achieve continuous availability if one region fails.
  • By Default, Designer and DAS containers run as a Genesys user (uid:gid 500:500). For this reason, the shared volume must have permissions that will allow write access to uid:gid 500:500. The optimal method is to change the NFS server host path to the Genesys user: chown -R genesys:genesys.
  • The Designer package includes a sample YAML file to create an NFS server. Use this only for a demo/lab setup purpose.
  • Azure Files Storage - If you opt for Cloud storage, then Azure Files Storage is an option to consider and has the following requirements:
    A Zone-Redundant Storage for RWX volumes replicated data in zone redundant (check this), shared across multiple pods.
    • Provisioned capacity : 1 TiB
    • Baseline IO/s : 1424
    • Burst IO/s : 4000
    • Egress Rate : 121.4 MiBytes/s
    • Ingress Rate : 81.0 MiBytes/s

Network requirements

• If Designer and DAS are accessed from outside of a K8s cluster, it is recommended to deploy/configure an ingress controller (for example, NGINX), if not already available. Also, the Blue-Green deployment strategy works based on the ingress rules.
• The Designer UI requires Session Stickiness. Configure session stickiness in the annotations parameter in the values.yaml file during Designer installation.

Browser requirements

Unless otherwise noted, Designer supports the latest versions of the following browsers:

• Mozilla Firefox
• Google Chrome (see Important, below)
• Microsoft Edge
• Apple Safari

Internet Explorer (all versions) is not supported.

Important

For Google Chrome, Designer supports the n-1 version of the browser, i.e. the version prior to the latest release.

Minimum display resolution

The minimum display resolution supported by Designer is 1920 x 1080.

Third-party cookies

Some features in Designer require the use of third-party cookies. Browsers must allow third-party cookies to be stored for Designer to work properly.

Genesys dependencies

The following Genesys dependencies are mandatory prerequisites:

• Genesys Web Services (GWS) 9.x
  • Configure GWS to work with a compatible version of Configuration Server.
• Other Genesys Components
  • Authentication Service
  • Voice Microservices

For the order in which the Genesys services must be deployed, refer to the Order of services deployment topic in the Setting up Genesys Engage cloud private edition document.

GDPR support

Content coming soon