This lesson's interactive features are locked, please to keep using them
Tunnel
In production, once you have a Gateway configured and have pointed your domain name to it (and perhaps its load balancer), you can access your application from anywhere in the world. The trouble is, we're using Minikube and the cluster is running on our local machine, and not only that, it's running in an isolated virtual machine.
Fear not! Minikube has a command that will forward the Gateway to your local machine.
Assignment
If you already started a tunnel in the previous lesson, keep it open. Otherwise, open a tunnel to your cluster (You might need to enter your password):
minikube tunnel -c
We'll be using the tunnel a lot in the rest of the course, I recommend you keep it open in a separate terminal window.
The tunnel should expose the Gateway controller's load balancer to your local machine on the Gateway IP you mapped to synchat.internal and synchatapi.internal in the previous exercise.
While the tunnel is open, navigate to http://synchat.internal in your browser. You should see the web app! The JSON API should also be available at http://synchatapi.internal (the root of the API should return a 404, but /healthz should return a 200).
Once you've confirmed that you can access the web app via a web browser, answer the question on the right.
Linux/Windows (WSL)
If the tunnel doesn't bind correctly, try: minikube tunnel --bind-address="127.0.0.1" -c