Skip to main content
Before you begin, ensure you’ve completed all of the previous sections to deploy required infrastructure and to set environment variables that this section requires.
Now that we’ve deployed all of the infrastructure into Google Cloud, we’ll set up some tools on your Kubernetes cluster:
  • Istio, a service mesh that will ensure that communication between different Rasa product components is encrypted in transit.
  • ExternalDNS, a tool that will allow the cluster to create the DNS records it needs automatically using GCP Cloud DNS.
  • Cert-manager, a tool to ensure we can automatically issue and renew TLS certificates for secure communication.
We’ll use scripts from our deployment-playbooks repo throughout this section to make things easier. If you’d like to understand more about exactly what each script is doing, open it in your IDE of choice and review the comments which explain what is being deployed at each step.

​
Cluster Setup

Firstly, we’ll set Istio on your cluster, the service mesh that will ensure that communication between different Rasa product components is encrypted in transit, on your cluster. To deploy the required infrastructure into your GCP environment, use the provided script in our companion repo:
The final output of this script will instruct you to create an NS DNS record for the domain you’re using. Check your DNS provider’s documentation for more information about how to do this. Once you have updated your DNS registrar with the zone name servers, wait for the DNS propagation. You cam verify if zone is properly delegated to GCP with command:
It should print the same GCP nameservers that were output at the end when you ran ./gcp/configure/configure-cluster.sh above. If so, you can continue further on with the playbook.

​
Install external-dns

We will now install external-dns onto our cluster. This tool allows your Kubernetes cluster to create the DNS records it needs automatically using the GCP Cloud DNS zone that you’ve just configured.

​
Install cert-manager

We will now install cert-manager which will handle issuing TLS certificates automatically using LetsEncrypt.
You may see a warning stating Warning: spec.privateKey.rotationPolicy: In cert-manager >= v1.18.0, the default value changed from Never to Always.. This is fine.

​
Collect Required Parameters

Most of the infrastructure work is now done, so we’ll gather together some info that we’ll use later in the playbook to make deploying the Rasa applications a bit easier. Collect some information about the GCP infrastructure you’ve deployed and set them as environment variables:
These environment variables are now set and ready to be used in your application configurations.

​
Test Ingress Setup

We’ve deployed and configured tooling onto the cluster to manage the creation of DNS records and TLS certificates. In this section, we’ll test whether it’s all working properly by temporarily deploying a tiny HTTP server called HTTPBin to check. If the test fails, the script will suggest some commands you can run to help identify the source of the issue.
You may see a warning stating Warning: spec.privateKey.rotationPolicy: In cert-manager >= v1.18.0, the default value changed from Never to Always.. This is fine.