Welcome to the Lab Guide for our Deploying Containerized Applications on Google Kubernetes Engine (GKE) lab. This article addresses challenges a student can have connecting via SSH. For issues regarding errors accessing the Marketplace during this lab, go here.
In this lab you will learn different ways to deploy applications and manage a GKE cluster. You will first deploy a single-container game application followed by a multi-container application (WordPress) provided by the Google Cloud Platform Marketplace. Along the way, you will learn about the architecture of GKE clusters, how to connect to GKE clusters using the popular Kubernetes command line tool
kubectl, and understand some of the ways that GKE integrates with other Google Cloud services.
Here are the steps required to make sure you are able to connect via SSH:
Ensure that the environment has loaded 100% before starting:
Log in to GCP using an incognito tab and use the provided credentials for the session.
Once you get to 'Authenticating gcloud' in the lab's Virtual Machine, go to 'compute engine' and choose the VM instance named 'ca-lab-vm'.
Click the down arrow in the Connect section and click on Open in browser window:
Wait for the window to load, this will take a few seconds. You may close the below message:
Enter the following command to begin authenticating gcloud with your lab account:
Copy the link that will populate and open a new window to paste it:
When prompted for the username and password, use the credentials provided for the lab session.
Copy the code:
Paste the code and you should be authenticated:
If by any chance the window refuses to load, please ensure that both your device and network are not blocking the environment from loading. Here are some troubleshooting tips:
- Open an incognito browser and test the URL from there. log-in if asked.
- Ensure direct network connectivity as connecting via VPN/ proxy tends to block connection.
- Please make sure no antivirus software or firewall settings are blocking the environment from opening.
- Try a different browser and log back in, allow cookies if prompted.
- Mandatory steps to isolate the issue:
- Use a different network.
- Try opening the lab using a different browser and device, especially if the device or network used is company issued.
Note that our policies are very strict and any small change can compromise the lab. Make sure you selected the correct region and that all settings, values, and names are exactly as described in the instructions. Also, take a look at our Help Center article Troubleshooting Problems With Labs.
Please sign in to leave a comment.