Deploying ToolJet on Kubernetes (GKE)
You should setup a PostgreSQL database manually to be used by ToolJet. We recommend using Cloud SQL since this guide is for deploying using GKE.
Follow the steps below to deploy ToolJet on a GKE Kubernetes cluster.
- Create an SSL certificate.
curl -LO https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/certificate.yaml
Change the domain name to the domain/subdomain that you wish to use for ToolJet installation.
- Reserve a static IP address using
gcloud
cli
gcloud compute addresses create tj-static-ip --global
- Create k8s deployment
curl -LO https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml
Make sure to edit the environment variables in the deployment.yaml
. You can check out the available options here.
If there are self signed HTTPS endpoints that Tooljet needs to connect to, please make sure that NODE_EXTRA_CA_CERTS
environment variable is set to the absolute path containing the certificates. You can make use of kubernetes secrets to mount the certificate file onto the containers.
- Create k8s service
curl -LO https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/service.yaml
- Create k8s ingress
curl -LO https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/ingress.yaml
Change the domain name to the domain/subdomain that you wish to use for ToolJet installation.
- Apply YAML configs
kubectl apply -f certificate.yaml, deployment.yaml, service.yaml, ingress.yaml
It might take a few minutes to provision the managed certificates. Managed certificates documentation.
You will be able to access your ToolJet installation once the pods, service and the ingress is running.
If you want to seed the database with a sample user, please SSH into a pod and run:
npm run db:seed:prod --prefix server
This seeds the database with a default user with the following credentials:
emai: dev@tooljet.io
password: password