The script creates an own DNS-Zone on GCP for Gitpod to avoid any interferences with other projects. If a subdomain is used an extra resource could create a domain delegation to the DNS-Zone created by the script.

If the parent domain is also hosted on GCP the resource looks like this:

resource "google_dns_record_set" "delegation" {
  name         = module.dns.zone.dns_name
  type         = "NS"
  ttl          = 300
  managed_zone = "<PARENT_DOMAIN>"
  rrdatas      = module.dns.zone.name_servers
  project      = "<PARENT_PROJECT_ID>"

  depends_on = [
    module.dns.done
  ]

}

A best practice would be to set up an extra GCP project (PARENT_PROJECT_ID) with a DNS-Zone managing the PARENT_DOMAIN.

Terraform backend

If the Terraform deployment should be shared in a team it is useful to create a backend storing the Terraform state (https://www.terraform.io/docs/backends/index.html).

Therefore a Google storage bucket could used:

terraform {
  backend "gcs" {
    bucket  = "tf-state-prod"
    prefix  = "terraform/state"
  }
}

https://www.terraform.io/docs/backends/types/gcs.html

Setup

A file has to be created to set every variable needed by the Terraform script, i.e. project.auto.tfvars. Using the ending .auto.tfvars the file is automatically recognized by Terraform.

project   = "PROJECT_ID"
region    = "europe-west3"
dns_name = "your-domain.com"
container_registry = {
  location = "EU"
}
certificate_email = "certificates@your-domain.com"

Several OAuth provider could be added (docs.gitpod.io).

Installation

After the variables are set up, the installation could be started.

$ make install