How-To: Set-up Dockup Agent on GCP

Create a kubernetes cluster

First sign up for GCP account if you don't have one. You can do it by heading over to console page. Once signed up, create a project called "dockup" and complete setting up billing. Note down project id of the project created. This id will come handy while configuring agent.

NOTE: You will get free $300 credit when you sign up for the first time

After you setup your GCP account, head over to kubernetes cluster page, enable kubernetes api, and create a cluster. It's okay to go with all default values. Please make a note of the name, and zone as we will be using them later. Create page looks like this

Cluster creation will take sometime. Please wait till it is complete.

Verify connection to cluster

# Install google cloud SDK. Using homebrew:
> brew cask install google-cloud-sdk
# Authorize yourself so that you can access projects
> gcloud auth application-default login
# See if you can get a list of projects. You should see the project that
# you have created here.
> gcloud projects list
# Set the current project.
> gcloud config set project dockup
# Get credentials for newly created kubernetes cluster.
> gcloud container clusters get-credentials <name-of-cluster> \
# Install kubectl and ensure that you are able to list pods
# without any errors.
> brew install kubectl
> kubectl get pod --all-namespaces
# Install helm. Using homebrew:
> brew install kubernetes-helm
# Install helm on kubernetes cluster:
> helm init
> kubectl create serviceaccount --namespace kube-system tiller
> kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin \
> kubectl patch deploy --namespace kube-system tiller-deploy \
-p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'
> kubectl create clusterrolebinding <your-name>-cluster-admin-binding \
--clusterrole=cluster-admin --user=<your-email-used-for-gke>
# You should be able to list helm installations without any error:
> helm list

Install dockup agent

Once you have kubectl and helm installed and configured, you need to install dockup agent. Fetch your Agent API key by going to

> helm repo add dockup
> helm install \
--set agent.dockupApiKey="<agent-api-key-from-settings>" \
--name=dockup-agent \

Once agent is installed, refresh and ensure that agent status is online.

Configure DNS

Next, you will install traefik which will be the loadbalancer for your kubernetes cluster. If you need auto-renewed Letsencrypt SSL, contact mentioning your DNS provider. The following command installs traefik without SSL.

> helm install \
--set rbac.enabled=true \
--name=traefik \
# Get "EXTERNAL-IP" for traefik from the output of the following command.
> kubectl get service

Add an A record in your DNS provider to point to the EXTERNAL_IP you got from the previous command.

For example, if you own "" and you want your deployment URLs to be "<random_urls>", then your base domain is and your DNS A record will have key: *.dockup and value: <value of EXTERNAL-IP>

Now you can go back to and update the base domain. In the above example, the value will be "". Once this is done, you are ready to start deploying!

Configure Agent

Configure base domain

After installing agent, you would have configured DNS. You need to specify the key and domain name without wildcard for agent.

For example, if you own "" and you want your deployment URLs to be "<random_string>", then your base domain is and same should be configured in agent settings.

Configuring registry

After creating project in google, you would have made a note of project id. Prepend this project id with and update registry for agent.

For example, if the id of project created is dockup-acme, then the value of registry will be