Configure the ingress to your Gitpod installation

⚠️ Deprecated Content

The content of this page assumes you are using Helm, which is now deprecated. Please use the Installer instead.

Configuring ingress into your Gitpod installation requires two things:

• three DNS entries pointing at the IP of Gitpod’s proxy service, and
• HTTPS certificates.

1. DNS Entries

Gitpod requires a domain resolvable by some nameserver (typically a public domain name, e.g. your-domain.com). As Gitpod launches services and workspaces on additional subdomains it also needs two wildcard domains. For example:

your-domain.com .your-domain.com .ws.your-domain.com

Installing Gitpod on a subdomain works as well. For example:

gitpod.your-domain.com .gitpod.your-domain.com .ws.gitpod.your-domain.com

1. Setup A records for all three (sub)domains. To learn your installation’s IP run:

   language: 

   bash

   copy code

   copied successfully

   kubectl describe svc proxy | grep -i ingress

2. Merge the following into your values.custom.yaml file:

   language: 

   yml

   copy code

   copied successfully

   hostname: your-domain.com
   components:
     proxy:
       loadBalancerIP: <your-IP>

   Specifying the loadBalancerIP make sure it stays the same across all redeploys.

2. HTTPS

Gitpod requires HTTPS certificates to function properly. We recommend using Let’s Encrypt for retrieving certificates as we do for gitpod.io.

Important: The HTTPS certificates for your domain must include your-domain.com, *.your-domain.com and *.ws.your-domain.com. Beware that wildcard certificates are valid for one level only (i.e. *.a.com is not valid for c.b.a.com).

To configure the HTTPS certificates for your domain

1. Generate certificates and put your certificate files under secrets/https-certificates/:
   language: 

   text

   copy code

   copied successfully

   secrets/https-certificates:
     |- tls.crt
     |- tls.key

2. Generate the dhparams.pem file using:
   language: 

   bash

   copy code

   copied successfully

   openssl dhparam -out secrets/https-certificates/dhparams.pem 2048

3. Create a kubernetes secret using:
   language: 

   bash

   copy code

   copied successfully

   kubectl create secret generic https-certificates --from-file=secrets/https-certificates

4. Afterwards, do an helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.10.0 to apply the changes.

Using Let’s Encrypt to generate HTTPS certificates

The most accessible means of obtaining HTTPS certificates is using Let’s Encrypt. It provides free certificates to anybody who can prove ownership of a domain. Let’s Encrypt offers a program called certbot to make acquiring certificates as straightforward as possible.

Assuming you have certbot installed, the following script will generate and configure the required certificates (notice the placeholders):

language: 

bash

copy code

copied successfully

export DOMAIN=your-domain.com
export EMAIL=your@email.here
export WORKDIR=$PWD/letsencrypt

certbot certonly \
    --config-dir $WORKDIR/config \
    --work-dir $WORKDIR/work \
    --logs-dir $WORKDIR/logs \
    --manual \
    --preferred-challenges=dns \
    --email $EMAIL \
    --server https://acme-v02.api.letsencrypt.org/directory \
    --agree-tos \
    -d *.ws.$DOMAIN \
    -d *.$DOMAIN \
    -d $DOMAIN

# move them into place
mkdir -p secrets/https-certificates
cp $WORKDIR/config/live/fullchain.pem secrets/https-certificates/tls.crt
cp $WORKDIR/config/live/privkey.pem secrets/https-certificates/tls.key

Note: Do not refrain if certbot fails on first execution: Depending on the challenge used you might have to restart it once.