Documentation:HTCC:Dep:InstallingAndDeploying:9.0.0DRAFT

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

Kubernetes cluster:

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

  • Kubectl tool
  • Helm

Deploying GWS

1. Unpack the Genesys Applications package tarball and change to the kubernetes directory:
   

   $ cd kubernetes

2. Create an environment configuration file (gws.env) from template located
   • The versions of GWS applications should be specified by setting environment variables in the created gws.env file:
     

     export GWS_SOME_SERVICE_VERSION="9.0.000.00.470"

3. Run the environment file you have created and see all available commands:
   

   $ . ./gws.env

4. Import GWS applications docker images to the client's container registry.
5. Deploy GWS infrastructure using gws-infra-deploy.sh script.The script will deploy GWS dependency servers - ElasticSearch, Redis, Consul, etc., at your Kubernetes cluster.
6. Deploy GWS microservices using gws-app-deploy.sh script.
7. Initialize GWS using gws-postdeploy.sh script.

Important

Running the command with the delete parameter will allow deleting the infrastructure or apps stack

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.