Running Gitpod in Amazon EKS

Provision an EKS cluster

Before starting the installation process, you need:

• An AWS account with Administrator access
  • Create one now by clicking here
• A SSL Certificate created with AWS Certificate Manager
• AWS credentials set up. By default, those configs are present in $HOME/.aws/.
• eksctl config file describing the cluster.
  • Here is an eks-cluster.yaml you can use as example.
• A .env file with basic details about the environment.
  • We provide an example of such file here.
• Docker installed on your machine, or better, a Gitpod workspace :)

Choose an Amazon Machine Image (AMI)

Please update the ami field in the eks-cluster.yaml file with the proper AMI ID for the region of the cluster.

Region	AMI
us-west-1	ami-0f3e6671ef1ede777
us-west-2	ami-04a6d2a3b0d131841
eu-west-1	ami-0542a7d18c5df4e79
eu-west-2	ami-060cb8be1976f9dd5
eu-central-1	ami-0d58b84ef791d4348
us-east-1	ami-0efd7bb7f07150aa3
us-east-2	ami-08b5bc88b0131552f

To start the installation, execute:

make install

Important: DNS propagation can take several minutes until the configured domain is available!

The whole process takes around forty minutes. In the end, the following resources are created:

• an EKS cluster running Kubernetes v1.21

• Kubernetes nodes using a custom AMI image:

  • Ubuntu 21.10
  • Linux kernel v5.13
  • containerd v1.5.8
  • runc: v1.0.1
  • CNI plugins: v0.9.1
  • Stargz Snapshotter: v0.10.0

• ALB load balancer with TLS termination and re-encryption

• RDS Mysql database

• Two autoscaling groups, one for gitpod components and another for workspaces

• In-cluster docker registry using S3 as storage backend

• IAM account with S3 access (docker-registry and gitpod user content)

• calico as CNI and NetworkPolicy implementation

• cert-manager for self-signed SSL certificates

• cluster-autoscaler

• Jaeger operator - and Jaeger deployment for gitpod distributed tracing

• metrics-server

• gitpod.io deployment

• A public DNS zone managed by Route53 (if ROUTE53_ZONEID env variable is configured)

Verify the installation

First, check that Gitpod components are running.

kubectl get pods
NAME                               READY   STATUS    RESTARTS   AGE
blobserve-6bdb9c7f89-lvhxd         2/2     Running   0          6m17s
content-service-59bd58bc4d-xgv48   1/1     Running   0          6m17s
dashboard-6ffdf8984-b6f7j          1/1     Running   0          6m17s
image-builder-5df5694848-wsdvk     3/3     Running   0          6m16s
jaeger-8679bf6676-zz57m            1/1     Running   0          4h28m
messagebus-0                       1/1     Running   0          4h11m
proxy-56c4cdd799-bbfbx             1/1     Running   0          5m33s
registry-6b75f99844-bhhqd          1/1     Running   0          4h11m
registry-facade-f7twj              2/2     Running   0          6m12s
server-64f9cf6b9b-bllgg            2/2     Running   0          6m16s
ws-daemon-bh6h6                    2/2     Running   0          2m47s
ws-manager-5d57746845-t74n5        2/2     Running   0          6m16s
ws-manager-bridge-79f7fcb5-7w4p5   1/1     Running   0          6m16s
ws-proxy-7fc9665-rchr9             1/1     Running   0          5m57s

TODO: add additional kubectl log commands

Test Gitpod workspaces

When the provisioning and configuration of the cluster is done, the script shows the URL of the load balancer, like:

Load balancer hostname: k8s-default-gitpod-.......elb.amazonaws.com

This is the value of the CNAME field that needs to be configured in the DNS domain, for the record <domain>, *.ws.<domain> and *.<domain>

After these three records are configured, please open the URL https://<domain>/workspaces. It should display the gitpod login page similar to the next image.

If the property ROUTE53_ZONEID is enabled in the .env file, we install external-dns and such update is not required

---

Update Gitpod auth providers

Please check the OAuth providers integration documentation expected format.

We provide an example here. Fill it with your OAuth providers data.

make auth

We are aware of the limitation of this approach, and we are working to improve the helm chart to avoid this step.

Destroy the cluster and AWS resources

Remove Cloudformation stacks and EKS cluster running:

make uninstall

The command asks for a confirmation: Are you sure you want to delete: Gitpod, Services/Registry, Services/RDS, Services, Addons, Setup (y/n)?

Please make sure you delete the S3 bucket used to store the docker registry images!