Documentation:HTCC:Dep:DeployingwithBashScripts:9.0.0DRAFT

Deploying with bash scripts

The following Kubernetes distributions are supported:

• Openshift (Fully Supported)
• GKE (Partially Supported)
• AWS EKS (TBD)
• Pure Kubernetes (TBD)

Requirements

1. Kubectl and Helm client utilities
   • Tiller is not required.
   1. For Openshift deployments, install the oc utility.
   2. For GKE deployments, install and configure the gloud utility/
2. The scripts reside in the gws-microservices hg repository.
3. Get your credentials and try using the utilities you've installed. We assume that your credentials are valid and they work without any errors.
   1. For non-GKE platforms: copy your configuration to ~/.kube/config and try "kubectl get nodes" and see the cluster nodes list.
   2. For GKE: follow the registration web-UI steps and try "gcloud container clusters list" and see all GKE clusters you have if any.
4. $ cd gws-microservices/infrastructure/kubernetes/gws-deployment # The "helm" directory actually contains all helm-charts we are using.
5. $ ls ../gws-settings # This will show you the environment files needed to source to operate a particular cluster with a particular environment.
6. $ . ../gws-settings/<YOUR ENVIRONMENT SOURCE FILE> # After you source the cluster/env variables, you'll see all available commands. To create your own environment file you can use the others as templates.
7. Import GWS-applications docker images to your container registry or add the GWS registries' keys to /etc/docker.d
   1. Internal Kubernetes clusters, deployed on Genesys premise: Get the registries' keys and add them to /etc/docker.d on all hosts, then restart docker.
   2. GKE. Get the GWS-microservices docker images tarball via any Genesys supply channel and import it to Google Container Registry as follows: "TARBALL=/full/path/to/GWS/apps/tarball push-containers-to-gke.sh"

Working with Prometheus and Grafana

Important

These services are deployed clusterwide and do not depend on GWS-applications' loads.

$ ./monitoring-deploy.sh delete
$ ./monitoring-deploy.sh

Working with GWS Infrastructure

$ ./gws-infra-deploy.sh delete
$ ./gws-infra-deploy.sh

Working with GWS Application Stack

$ ./gws-app-deploy.sh delete
$ ./gws-app-deploy.sh

Pulling Current GWS Applications Container

- $ STACK_DOCKER_IMAGE_PATH=gws-registry-usw1.genhtcc.com ./pull-containers.sh

DNS Requirements

All of the services, either cluster-wide, infrastructure or GWS-applications ingresses require DNS names to be pre-populated to get access to and for host-based naming virtualization.

• Openshift
• GKE

    XX.XX.XX.XX   grafana.gke.local
    XX.XX.XX.XX   consul.gke.local
    XX.XX.XX.XX   active.gke.local
    XX.XX.XX.XX   test.gke.local

Persistent Storage Requirements

• Openshift : the GlusterFS storage can be pre-populated manually.
• GKE : No specific configuration is required.
• No storage : Set the PERSISTENT_STORAGE=false in the environment file.