Skip to content

Latest commit

 

History

History
76 lines (42 loc) · 3.36 KB

MULTI_REGION.md

File metadata and controls

76 lines (42 loc) · 3.36 KB
Raw

GCP Multi-Server Single Region

This project will deploy Kasm Workspaces in a multi-server deployment in GCP within multiple regions of your choice. Each Kasm server role is placed in a separate subnet and you can optionally forward traffic from user sessions on the Kasm Agent through a NAT Gateway.

NOTE: Make sure you read and understand the GCP requirements before continuing!

Diagram

Pre-Configuration

Consider creating a separate GCP Project for the Kasm deployment.

DNS Zone

There are a couple of DNS options available with this GCP Terraform. Regardless of method, Terraform will:

  • Add a DNS record for the load balancer
  • Add a private DNS zone and add records for the private load balancer used by Agents to communicate with the webapps

  1. Create and verify the public DNS zone before deploying Terraform - Using this method, you will create a DNS zone or use an existing DNS zone in the same GCP Project where you deploy Kasm

  2. Allow Terraform to create the public DNS zone for you - Using this method, Terraform will create a public DNS zone using the values you provide, and you must manually add the name server (NS) records to the parent DNS zone so queries are forwarded correctly

Create Terraform service account and generate an API key

Create a GCP Service Account to use with Terraform (https://cloud.google.com/iam/docs/service-accounts-create), and generate an API key. Once the API Key credential file is downloaded, copy it's contents into the gcp_credentials.json file in this directory, and Terraform will use these credentials to perform all operations.

Recommended Service Account roles:

  • Compute Admin
  • DNS Administrator
  • Network Management Admin
  • Service Account Admin

GCP APIs to enable before running Terraform

There are several GCP service APIs that must be enabled before this Terraform can build successfully. In your GCP project, navigate to each of these and ensure they are enabled before running the Terraform configuration stage below.

GCP APIs:

  • Cloud DNS
  • Cloud NAT

Terraform Configuration

  1. Initialize the project

    terraform init

  2. Open terraform.tfvars and update the variable values. The variable definitions, descriptions, and validation expectations can be found in the variables.tf file, or in the README.

In order to deploy this in multiple regions, simply add all additional regions in the kasm_deployment_regions variable in the terraform.tfvars file. The first region in the list is where the Database will be deployed, thus, it is recommended to put this closest to those who will be responsible for Database administration to reduce network complexity and DB latency.

  1. Verify the configuration

    terraform plan

  2. Deploy

    terraform apply

  3. Login to the Deployment as an Admin via the domain defined e.g https://kasm.contoso.com

NOTE: The Load Balancer certificate can take between 15-45 min. to become active so you can access your Kasm deployment.

  1. Navigate to the Agents tab, and enable each Agent after it checks in. (May take a few minutes)

Detailed Terraform Deployment Diagram

Detailed Diagram