Jump to: navigation, search
Line 24: Line 24:
 
*:* Microsoft Internet Explorer 11
 
*:* Microsoft Internet Explorer 11
 
*:* Microsoft Edge
 
*:* Microsoft Edge
 +
 +
==Configuring Web Services Applications==
 +
To configure Web services and applications, refer to [[Documentation:HTCC:Dep:ConfigurationPremise|Configuring Web Services and Applications]].
  
 
== Deploying GWS ==
 
== Deploying GWS ==

Revision as of 04:38, February 5, 2020

Deployment of Web Services and Applications in Kuberbetes

Important: This content is restricted and not viewable without a login supplied by Genesys. The information contained in this documentation is not considered final and is managed under the terms and conditions found in the Pre-release Agreement. This documentation provides the most up-to-date reference information available for this pre-release version and is restricted for use by those who have signed the Pre-release Agreement with Genesys to acquire an early version of the software.

Prerequisites

Hardware Requirements

The solution can be deployed at a Kubernetes cluster with a minimal size of 3 nodes with an overall amount of 64 GB RAM. Recommended hardware requirements for each Kubernetes node:

  • Nodes: 3 nodes (Virtual Machines)
  • RAM: Approximately 22 GB for each node (64 GB in total)
  • CPU: 15 cores for each node (45 cores in total)
  • HDD: 100 GB for each node

Software Requirements

  • OS: CentOS-7

Kubernetes cluster:

  • Rancher Kubernetes Deployment
  • Client-side utilities installed at deployment host:

Workspace Web Requirements

  • Browser:
    • Google Chrome 75+
    • Mozilla Firefox 68+
    • Firefox ESR 60.9
    • Microsoft Internet Explorer 11
    • Microsoft Edge

Configuring Web Services Applications

To configure Web services and applications, refer to Configuring Web Services and Applications.

Deploying GWS

To be updated


DNS and Storage Requirements

All of the services ingresses require DNS names to be pre-populated to get access to.

  • Openshift: the GlusterFS storage should be pre-populated manually.
  • NFS (for premise deployments) - should be pre-populated manually.
  • GKE - just works out of the box, no further interaction required.
  • AWS - dynamic storage provisioning works out of the box.
  • No storage - just set the PERSISTENT_STORAGE to false variable in your environment file.
Comments or questions about this documentation? Contact us for support!