Cloud Shell / Cloud Code - Deep Dive

1. Overview

Cloud Shell is an online development and operations environment accessible anywhere with your browser. You can manage your resources with its online terminal preloaded with utilities such as the gcloud command-line tool, kubectl, and more. You can also develop, build, debug, and deploy your cloud-based apps using the online Cloud Shell Editor

In this lab, you will work with Cloud Shell, Cloud Shell Editor, creating and deploying and testing container-based applications using Cloud Code on local emulators and on the real services.

What you will learn

  • Navigate and get familiar with Cloud Shell main features
  • Practice with different Cloud Shell usage patterns
  • Customize your Cloud Shell environment for advanced use
  • Get familiar with Cloud Code options and features
  • Know the details of Cloud Code for Kubernetes applications
  • Deploy and debug Containerized applications with Cloud Code on Cloud Shell Editor
  • Use local emulators like Minikube


  • You will need a GCP project with Editor permissions, a GCP account and access to Cloud Shell
  • For the optional parts, you'll need a terminal emulator and the Google Cloud SDK installed.

2. Setup and Requirements

Self-paced environment setup

  1. Sign-in to the Google Cloud Console and create a new project or reuse an existing one. If you don't already have a Gmail or Google Workspace account, you must create one.




  • The Project name is the display name for this project's participants. It is a character string not used by Google APIs, and you can update it at any time.
  • The Project ID must be unique across all Google Cloud projects and is immutable (cannot be changed after it has been set). The Cloud Console auto-generates a unique string; usually you don't care what it is. In most codelabs, you'll need to reference the Project ID (and it is typically identified as PROJECT_ID), so if you don't like it, generate another random one, or, you can try your own and see if it's available. Then it's "frozen" after the project is created.
  • There is a third value, a Project Number which some APIs use. Learn more about all three of these values in the documentation.
  1. Next, you'll need to enable billing in the Cloud Console in order to use Cloud resources/APIs. Running through this codelab shouldn't cost much, if anything at all. To shut down resources so you don't incur billing beyond this tutorial, follow any "clean-up" instructions found at the end of the codelab. New users of Google Cloud are eligible for the $300 USD Free Trial program.

3. Working with Cloud Shell Terminal

In this section, you will learn about the Cloud Shell Terminal, how to navigate the UI, use the features, and explore the configuration options and different ways to use it to help you boost your productivity.

Cloud Shell has two main tools, the Cloud Shell Terminal and the Cloud Shell Editor. In this lab the terms Cloud Shell Terminal and Cloud Shell will be used interchangeably, however the Editor will always be referred to as Cloud Shell Editor to make a clear distinction between the terminal emulator and the IDE.

Cloud Shell is a fully functional cloud-based Shell built on top of an ephemeral Google Compute Engine Debian-based Linux machine that's always available for you to use. It comes with Google Cloud SDK installed and several relevant tools like git, kubectl, kubectx, curl, python3, tmux...

Your $HOME directory is persisted in Cloud Storage by Google Cloud and mounted automatically each time the Cloud Shell machine starts, so you won't lose any information that you leave under it even if the Cloud Shell machine shuts down. That means if you enable Cloud Shell again, your $HOME directory and any customization you may have done to it will be there for you to use.

Launching Cloud Shell

  1. Go to and if not already logged in in the GCP console, enter your Google credentials. You will be presented with the Google Cloud Platform's Console main UI.
  2. Select the GCP Project ID you'll be working with in the Cloud Console menu bar selector:


  1. Find the button to activate Cloud Shell in the right side of the menu bar, next to the avatar of your account:


  1. Click the Cloud Shell icon and the Cloud Shell Terminal will open, revealing a new pane right under the GCP Console UI: UI:


In this pane, you have what is called the Cloud Shell Terminal.

  1. Go to the Cloud Shell Terminal, and notice that as you selected the proper GCP Project ID from the GCP console, Cloud Shell knows about it so you don't have to specify it again:

This will output your GCP Project ID, which is also shown in the Cloud Shell prompt.

Switching between tools

Cloud Shell gives you several tools and configuration options. Review them through the options available in the Cloud Shell Menu:


  1. Click the button 67bd0e39332a8438.png in the bar that will allow you to maximize Cloud Shell Terminal and occupy all your browser's tab real estate:


  1. Cloud Shell maximizes and occupies the full browser tab space:


  1. Click it again. The browser tab real estate will revert to being shared between the Cloud Console and Cloud Shell.

Opening new tabs

Cloud Shell Terminal allows you to open as many tabs as you need.

  1. Click the following button and open a new tab.


  1. Now close the new tab clicking on the x next to the tab name or typing exit in the corresponding shell:


Opening a new window

Opening Cloud Shell in a new browser window allows you to have the Cloud Console in one window and Cloud Shell in another one.

  1. Click the following button and observer how Cloud Shell opens in a new browser tab:


  1. Notice that Cloud Shell now offers the same toolbar options, but with a slight different look:


  1. Stay in this new browser tab throughout the next sections.

Transferring sessions with Tmux

Cloud Shell comes with tmux included. Tmux is a very popular terminal multiplexer, similar to GNU Screen. The integration with tmux gives Cloud Shell the ability to preserve your session no matter where you are.

In the following steps you will practice with this concept to better understand the feature.

Moving the Cloud Shell Terminal around

  1. In the Cloud Shell tab that you just opened, type the command top:


The top command provides a real time view of the processes running in your Cloud Shell Terminal. You will use it to visualize the session persistence in Cloud Shell provided by tmux.

  1. Return to the first tab in your browser (the one where the Cloud Console is).
  2. Observe that, because you previously decided to open Cloud Shell in a new window, there's a message saying "Your session was transferred to another browser tab. You can disable this from the "Tmux Settings" option in the Cloud Shell settings menu."
  3. Click on the reconnect button:


You will then have access to the shell that was running in the second tab, and top continues running here just as you just left it.

  1. Navigate to the second tab in your browser, where you opened Cloud Shell in a new window,
  2. Click Reconnect. You will recover the top process just as it was running before we closed the window.

Splitting Windows with Tmux

Tmux is far more useful than what you just used it for. A tmux tutorial is out of the scope of this lab, you can find more information about it in the official tmux getting started.

However, tmux gives Cloud Shell some additional features that are possible in local terminal emulators. To demonstrate one, you will do a side-by-side terminal split.

  1. Inside the Cloud Shell, press Ctrl + b, and then %
  2. Observe how tmux creates a new pane right to the original one:


  1. Click on the second pane and type exit.

Utilize Web Preview

Cloud Shell can also establish automatic port forwarding from the Cloud Shell machine running in the cloud through your local browser running in your computer.

  1. Type in Cloud Shell:
python3 -m http.server 8080
  1. Go to the Web Preview option in the upper right corner and select Preview on port 8080:


A new tab will open with the default page that's served in that port.

Note that you can change the port and do a preview for whatever port your application is exposing in Cloud Shell, not just port 8080.

Accessing Additional Cloud Shell options

There are additional settings and options available in Cloud Shell.

  1. Click the three dots in the Cloud Shell menu to access the options:


The most relevant options here are the possibility to upload or download files to Cloud Shell, and restart the Cloud Shell machine in case you experience any issues.

4. Working with Cloud Shell Editor

One of the most important features of Cloud Shell is the Cloud Shell Editor. This is a full fledged IDE based on the Open Source Project Eclipse Theia and contributed to by Google amongst others. The look and feel is very similar to VSCode as both use several common Open Source base components, such as the Monaco editor, the Extension model, the Language Server Protocol and the Debug Adapter Protocol.

As Theia/Cloud Shell Editor is a quite complex tool, describing all Cloud Shell Editor features is out of the scope of this lab. In this section you will walk through some core concepts and unique features available in this Google Cloud implementation.

Accessing Cloud Shell Editor

Cloud Shell Editor can be accessed in three different ways:

  • Access from the command line
  • Access through Cloud Shell menu
  • Visiting a URL in your browser

Experience these methods through the following steps

  1. Open the .bashrc from the command line with the following command:
cloudshell edit $HOME/.bashrc
  1. Open Cloud Shell from the menu, by clicking on the Open Editor 6039dbc755bfca9f.pngbutton: f493b9a98771b0af.png This opens the Cloud Shell Editor while keeping open the Cloud Shell Terminal. If you wish to have all the tab real estate for just Cloud Shell Editor, click on the button right to the Edit button to close the terminal. These two buttons (Open/Close Editor and Open/Close terminal) will determine which of the tools is present in the browser tab. Practice clicking on both to get the knack of it.
  2. Invoke the Cloud Shell Editor from the URL bar in the browser, by typing

Using the command line from Cloud Shell Editor

Although you have Cloud Shell Terminal and Cloud Shell Editor coexisting in the same browser tab, you can dispense with Cloud Shell Terminal and use exclusively Cloud Shell Editor, and the terminal available from inside Cloud Shell Editor, for all your needs. This may make sense if you're used to living inside the IDE and know the different shortcuts and pane dynamics from VSCode.

Open the Cloud Shell Editor using any of the methods mentioned above. Then, go to the Editor menu and select Terminal > New Terminal (or press `Ctrl + `` in your keyboard). A new terminal pane will open in the lower part of Cloud Shell Editor that you can use for all your shell needs:


This will also give you the option to manage different terminal panes without the need to use tmux pane management as it was the case for Cloud Shell Terminal.

Customizing Cloud Shell Settings

Cloud Shell offers several customization options, from look & feel and basic behavior, to Cloud Shell Terminal startup configuration and detailed operation. You will review the different options in some detail in the following sections.

Go to the Cloud Shell Terminal menu and click on the cog icon. Several configuration options will appear:


Review some of them:

  • Color Themes: you can use Light, Dark , or use a set of custom colors (basic one, like font color and background color)
  • Text size: 5 different font sizes to choose from
  • Font: Courier new or Monospace
  • Copy settings: here you can change the copy keyboard shortcut to resemble the shortcuts used in most popular Linux terminal emulators.
  • Keyboard: mapping the Meta key to Alt (by default, Meta is ESC) and mapping of the Alt Gr Key in some OSs.

Configuring the Shell Environment

As a Terminal emulator running a shell in a Debian-based Linux machine, you can customize your shell environment the same way you do it in Linux. As such, any configuration files present in $HOME (like .bashrc) will be sourced each time a new login shell process is created.

Cloud Shell also gives you the ability to specify which actions you want to perform every time the Cloud Shell instance is started in a special configuration file called .customize_environment. You can read more about this in the Environment Customization documentation.

Practice adding some configuration to Cloud Shell Terminal. Go to the Cloud Shell terminal and clone the following sample code repo:

git clone

This repo contains samples for the two main events where you may want to configure your Cloud Shell:

  • Whenever the Cloud Shell instance starts: the file $HOME/.customize_environment will be read. The execution log for this process can be found in /var/log/customize_environment and a /google/devshell/customize_environment_done will be created upon successful execution.
  • Whenever a new shell process is started (new window, new tab...); the regular bash shell configuration files will be read.

Practice with both by following these steps:

  1. Execute the following command to launch the customizations provided by the repo:
cd cloud-code-getting-started

This sets up both customization options previously mentioned and enables them.

  1. Notice the new shell prompt. A bash script sourced in .bash_profile file has configured this new prompt that's shorter than the default one, and includes basic Git information like the checked out branch or git status.
  2. There's now a new code alias to the cloudshell edit command that's shorter. Use it to see the contents of the .bash_profile file:
code $HOME/.bash_profile
  1. Use the newly installed command bat to see the contents of the .customize_environment file:
bat $HOME/.customize_environment

bat is an enhanced version of the popular Unix tool cat. The bat output is showing here the apt install command used to reinstall hey, a load testing tool, each time a new Cloud Shell machine is spun up.

  1. Test that everything is working by clicking in the Cloud Shell menu (the three dots in the upper right corner) and selecting Restart. When asked for a reason, select "Want clean VM state"

This will allow you to simulate Cloud Shell timeout and instance recreation, making sure that everything is configured correctly.

Customizing the Cloud Shell Container Image

This customization option allows you to create a Docker image that functions as a custom Cloud Shell environment with additional packages and custom configurations. The image generated will spin up a fully ephemeral Cloud Shell instance, so neither the Cloud Shell VM nor the $HOME directory attached to it will persist. Doing this Image creation will however be useful for use cases where you need to deliver function-specific Cloud Shell instances to third parties so they can perform a specific task in the most efficient way.

Instead of customizing the environment as you did in the previous section, you will bake your changes in a new image that's used to spin up your Cloud Shell. This has obvious advantages as your custom Cloud Shell will start faster.

Creating a new Cloud Shell image

  1. Start the Cloud Shell container image creation by typing in Cloud Shell Terminal:
cloudshell env create-custom-image custom-cloud-shell
cd custom-cloud-shell

This creates a new directory in your Cloud Shell and a new Cloud Source Repositories repo with the same name to host your code. It also clones a sample Dockerfile in the $HOME/custom-cloud-shell/ directory.

  1. Add the line RUN apt install -y hey to the last line of the Dockerfile:
echo "RUN apt install -y hey" >> $HOME/custom-cloud-shell/Dockerfile

This sets up the same customization you had in the .customize_environment, but baked in a container instead.

  1. Build the image locally:
cloudshell env build-local
  1. Test the new image by executing the following command:
cloudshell env run

You will now be in a shell inside the image.

  1. Test that the hey command is installed by running it:
  1. When finished, type exit to exit the container:
  1. Push the changes to the Cloud Source Repository and the image to Container Registry:
git commit -a -m "Initial commit"
git push origin master
cloudshell env push

Testing the new image

  1. Make the image publicly available so you can consume it:
gsutil iam ch allUsers:objectViewer $(gsutil ls)
  1. Generate a URL that you can use to test your published Cloud Shell custom instance:
echo "$GOOGLE_CLOUD_PROJECT/custom-cloud-shell"
  1. Copy the output URL and paste it in a new browser tab, and the Cloud Shell custom instance will open. Note how when you access the instance, there are banners indicating that you're running in full ephemeral mode:


  1. Test the image again running the hey command
  1. Once done, exit the ephemeral Cloud Shell instance, go back to the tab where your regular Cloud Shell was opened, and click Reconnect.

Access Cloud Shell Remotely with SSH

You can also use Cloud Shell features remotely from your local computer. This typically involves two different use cases:

  • SSH'ing to your Cloud Shell machine from your local terminal
  • Mounting your Cloud Shell remote $HOME directory locally.

For this, you'll need to have the Google Cloud SDK locally installed. You will also need to configure it with your project ID and the specific credentials that you're using.

Do the following steps from a terminal emulator running in your local machine:

  1. Set up the GCP Project ID and log in with the credentials corresponding to the Cloud Organization where you have your Cloud Shell.
gcloud config set projectid <your project id>
gcloud auth login
  1. SSH to your remote Cloud Shell machine:
gcloud cloud-shell ssh --authorize-session

You will now be in your Cloud Shell, but using the features and configuration of your local Terminal emulator. If the one you use supports tmux, you may take advantage of further integrations to have a better remote experience.

Mount your Cloud Shell home directory from your local machine

Although being able to SSH to the remote Cloud Shell instance is nice, it's even better to be able to have your local IDE with access to your remote Cloud Shell $HOME directory. This way, you can combine the SSH access demonstrated previously with the ability to edit remote code locally.

To do this, from your local machine, first create a mount point:

mkdir $HOME/cloudshell

This is the directory where your Cloud Shell will be mounted. Now, to mount it, make sure your Cloud Shell instance is started and then type in your local terminal:

$(gcloud cloud-shell get-mount-command $HOME/cloudshell)
cd $HOME/cloudshell

This will get the mount command that you need to issue to mount Cloud Shell locally, and mount it. You will see the contents of your Cloud Shell home directory mounted in your local machine.

Now, you can open an IDE like VSCode locally and open a workspace that's remote in the Cloud. At the same time, by using the SSH access to Cloud Shell, you may open a Terminal pane inside the IDE to also have a remote terminal integrated in your local IDE.

5. Using Cloud Code

Cloud Code is a plugin developed by Google that allows developers to work more effectively with cloud based tools. It's available in multiple IDEs and code editors such as VSCode and Jetbrains products and it's integrated by default into the Cloud Shell Editor for your convenience. Cloud Code includes plenty of developer friendly features that you'll be practicing with in the next steps.

Locating Cloud Code in your Cloud Shell Editor

Using the Quick Access Buttons

Find the following four buttons exposed in the left pane of the editor:


The first three icons in the left pane are respectively Cloud Run, GCP APIs and Cloud Secret Manager. These allow easy access and configuration to these GCP services straight from the Cloud Shell Editor.

  • Cloud Run: you'll quickly explore this feature later in this lab.
  • Cloud APIs: TBF
  • Cloud Secret Manager: TBF

In this lab, you will be focusing on the first (Cloud Run) and fourth icons (Kubernetes Clusters).

Using the status bar

There are two additional parts of Cloud Cloud exposed through the Cloud Shell Editor UI that are relevant. You can see both in the lower bar in the Editor:


  • <> Cloud Code: clicking here will expose a quick actions menu that you'll be using through this tutorial: e41eea698b135dd0.png
  • minikube: this will let you control the local kubernetes emulator, minikube, with basic actions like starting or stopping the cluster.

Create a Minikube instance now by clicking on the button.


Creating a GKE Cluster with Cloud Code

  1. Click the icon Cloud Code - Kubernetes Clusters ( 5ffab5cb541da6.png) on the left. You will see a new pane appearing on the left called CLOUD CODE - KUBERNETES: CLUSTERS.
  2. Click on the + button next to CLOUD CODE - KUBERNETES: CLUSTERS and select Google Kubernetes Engine (note that you could also choose other options like the Minikube you spun up before):


  1. Click on Create a New GKE Cluster. This option will load a new pane on the right where you can enter additional information to quickly create a Development Cluster. Follow the instructions in the panel and enter the following information:
  • Choose Autopilot
  • Select your region (europe-west-1)
  • Give your cluster the name "dev"
  1. Click the Create Cluster button. This will create a new Autopilot cluster.

The cluster creation process cant take up 5 five minutes. So while the cluster is being created, go ahead and explore a bit more of the Cloud Code Kubernetes Pane.

Exploring the Cloud Code Kubernetes pane

Earlier you created a Minikube cluster. When it's ready this cluster will appear in the Cloud Code Kubernetes pane with the name you gave it, local:


The cluster will appear as ACTIVE in the UI. This setting is in sync with the current kubernetes context in the command line. .

What you can see in the Cloud Code Kubernetes pane is the following:

  • The default KubeConfig file: Cloud Code reads the ~/.kube/config file for you user and uses it to connect to the Kubernetes Clusters configured there so you can easily navigate them. You can edit the Kubeconfig file by hovering over the Default Kubeconfig line and then clicking the square with the outgoing arrow next to it if you want.
  • A browsable renderization of the different objects of your registered clusters: in this case, you can see the local Minikube cluster that you created before, with its Contexts, Namespaces and Nodes. Go ahead and expand some of the nodes of the tree. There won't be any pods yet as you haven't deployed any application.

Once your new GKE cluster is up and running it will be shown in the left pane along with the local Minikube cluster. Note that you can right click on any of the clusters and make it "active" in the sense of selecting the cluster for any of the Cloud Code actions that you may launch:


Before proceeding, right click on the local Minikube cluster, and make sure it is marked as ACTIVE.

6. Working with Kubernetes applications in Cloud Code

Creating a new application

Another quite common way to interact with Cloud Code is through the Cloud Shell Editor command palette.

  1. Invoke the command palette (Ctrl + Shift + P or Cmd + Shift + P depending on your OS) and type Cloud Code to see all options that Cloud Code offers.
  2. From the command palette, select Cloud Code: New Application.


You'll be presented with a drop-down from where you can select different options.

  1. Select Kubernetes Application and then Go: Guestbook. You'll be presented with a new window asking you to select where to save the application code.
  2. Select the directory you're in and leave your application name as Guestbook. Cloud Code will reload your Cloud Shell Editor window and select the Guestbook directory as the active workspace.
  3. Invoke the Cloud Shell Editor command palette again and type run in Kubernetes. The option Cloud Code: Run in Kubernetes will appear.
  4. Select it and it will autosuggest using the local Minikube cluster, as it is the one that is active.
  5. Answer Yes.
  6. Observe the detail of what's going in the Cloud Shell Editor console output.
  7. Go to the upper left corner of the Cloud Shell Editor console output, click on the selector there, and select Run on Kubernetes -Detailed to see all that's going on:


Cloud Code: Run in Kubernetes is auto detecting the skaffold.yaml configuration that's in your application base directory. Through this configuration file, Skaffold is telling Cloud Code how to build and deploy the application for you. You'll look into more detail on Skaffold in future modules of this training.

  1. Wait for the building and deployment of the application containers to finish and show a success message in the Cloud Shell Editor console output: 7d40ddc989d55cc.png
  2. Hover over the go-guestbook-frontend service URL until the Open Web Preview link appears.
  3. Cmd + click (or Ctrl + click, if you're on Linux/Windows/Chrome OS) on the URL. You will see the Guestbook application main page:


This tab is tunneling the connection from your laptop to the actual URL where the service is listening. This is done automatically by Cloud Shell for you, so you don't need to worry about all the configuration steps involved to make such a thing happen.

Modifying your application code

Now that your application is running, you get to make changes in the source code and let the Cloud Code and Skaffold combination to hot reload these changes.

To try it out, follow these steps:

  1. Navigate to the **guestbook/src/frontend/templates** **directory** in Cloud Shell Editor and **double click on the** **home.tpl** **template file**. This file contains the template HTML used by the frontend service to render the home page of the application.
  2. Find the **<h1>** **tag** in the file and **change the title of the page**. For example, write "My Awesome Guestbook" instead of "My Guestbook".
  3. Observe in the Cloud Shell Edition console output that once you've finished making the change, Cloud Shell Editor autosaves the change and Skaffold triggers the automatic rebuild of your application.
  4. Navigate to the tab where the Guestbook app main page is and reload it, you'll see the change you just did right away.

Debugging your application code on Kubernetes

You will now see how Cloud Code can simplify Kubernetes debugging for us.

Set a breakpoint

Do the following steps to set a breakpoint in your code to inspect what's going on whenever you make a new request for the frontend service of your application.

  1. Go to the Cloud Shell Editor Explorer in the left pane ( c58bcb97c5d8e6f1.png icon) and navigate to the lower left pane where the active workspace with the application's directory is. Double click on guestbook/src/main.go to open it.
  2. Go to line 68 that starts with log.Printf("received request: ... and double click at the left side of the line number to set a breakpoint. This line is invoked every time there's a new request to your application frontend, so that you can inspect the request you've just received.


Enable Debug on Kubernetes

  1. From the Cloud Code Status Bar, select "Debug on Kubernetes" (you can also open the Cloud Shell Editor command palette and type "Debug on kubernetes" to access the same option). When prompted, answer the following questions:
  • "Use current context (local) to run the app?": answer Yes. This is just confirming that you want to deploy your application in your local Minikube cluster: cfec3656f9c4b8c1.png
  • Press ENTER twice when Cloud Code autofills for you the /app directory as the one where the app is deployed in the containers: 1a074e76a90adb61.png You need to do this action twice, one for the go-guestbook-front container and one for the go-guestbook-back container. In this case, the /app directory that was just filled in by Cloud Code was determined by extracting the path where the source code was COPIEd to from the Dockerfile. This autosuggestion might not always be possible by Cloud Code, hence the option to prompt the user here to provide the correct location.
  1. Observe the Cloud Code Output in the lower pane: the application is redeployed and Cloud Code inserts the necessary artifacts to be able to debug the application deployed in Kubernetes.
  2. In the upper right corner of the Cloud Code Output pane, select the Kubernetes: Run/Debug - Detailed view to see more details of what's going on:


Cloud Code attaches a debug session for each debuggable container in the application, and instructs Cloud Shell Editor to open the debugging pane. You could now perform the same tasks you normally do when debugging local code, like setting breakpoints as you did before and stepping through code, against a live Kubernetes cluster like the Minikube cluster where your app is running now.

  1. If not already opened, Cmd + click (or Ctrl + click) on the go-guestbook-frontend forwarded URL offered by the Output pane in Cloud Shell Editor. A new tab opens making a request to the front service.

Debug the app

  1. Observe the tab that just opened: the tab will have a spinning wheel, meaning that it's trying to load the application main page.
  2. Move back to the Cloud Shell Editor tab. You'll see that the Editor has entered debug mode. The front service main.go file is highlighting the breakpoint where the execution is stopped:


  1. Expand the CALL STACK and VARIABLES panes to the left of the breakpoint to get more details.
  2. Click on the continue button in the DEBUG controls exposed in the upper left pane:


  1. Check how the service resumes normal operation by observing Output pane with Run on Kubernetes - Detailed selected:


7. Working with Cloud Run applications in Cloud Code

Cloud Code also offers integrations and tooling to simplify development for Cloud Run, a Google Cloud managed container platform. In this section, you'll practice with them using both the Cloud Run emulator provided by the Google Cloud SDK and the Cloud Run service running in GCP.

Deploy and Debug with Cloud Run (Emulated)

Follow these instructions to deploy and debug a sample application using the Cloud Run local emulator provided by the Google Cloud SDK:

Enabling the Cloud Run API

  1. Select Cloud Code - Cloud Run (icon d88fc0daaaad5604.png) from Cloud Code's Quick Access (located at the left of the Cloud Code Editor)
  2. If asked to select a project, click on the blue button Select a project and select your project in the menu that will appear in the centered upper part of the Cloud Shell Editor where you want to work:


  1. You'll be asked to Enable the Cloud Run API: click on blue button to enable it:


  1. You'll get a confirmation dialog in the lower right part of Cloud Shell Editor: confirm the API enablement in your project by clicking on YES. After a while, the Cloud Run API will be enabled and you'll see that the Cloud Run Code Code pane activates for your project but shows no Cloud Run services being deployed (as you haven't deployed any yet):


Creating a new application

  1. Create a new Golang-based Cloud Run ready application: go to Cloud Code Status bar in the lower part of the Cloud Shell Editor (or press Cmd + p and type "New app" to do it from the command palette) and select New Application.. When the option Cloud Code: New Application appears, select it:


  1. You'll be asked to select a type of new application. Select the Cloud Run application option:


  1. Select the Go: Cloud Run application to clone/download the sample application code to a local directory of your Cloud Shell machine:


  1. Name the directory hello-world and click on Create New Application:


This will download the application code and will reload Cloud Shell Editor, setting the newly created directory as your active workspace.

Deploying the application with debugging enabled

You will now deploy and debug the application in the Cloud Run local emulator provided by Cloud Code.

  1. Navigate to the main.go file in the Cloud Shell Editor and set a breakpoint in line 62 by clicking on the left side of the line number. Observe how a red dot appears to the left of the line number, indicating an active breakpoint where the code will stop on each code invocation:


Setting the breakpoint here will also make the service enter debugging mode an pause each time you reload the service main page:

  1. Press Cmd + P (or Ctrl + p depending on your OS) and type "debug on cl". The option Cloud Code: Debug on Cloud Run Emulator will appear. Select it.
  2. A new Run/Debug on Cloud Run Emulator pane will open with a series of selections for you to do. Leave all the default settings, making sure that the Build Environment is set to local, and click on the Debug button:


  1. Deployment of the application will start. Go to the lower pane and select Cloud Run: Run/Debug Locally - Detailed to obtain more information on what's going on:


The local Cloud Emulator uses Minikube under the hood. If Minikube is not running already in your Cloud Shell machine, Cloud Code will start it automatically. Right after this happens, you'll see the application container being built.

  1. A new Cloud Code dialog will appear asking you if you want to debug the hello-world container that's being deployed. Press ENTER to confirm that the directory where the application is deployed in the container is the correct one:


  1. The deployment process will take some seconds. When finished, you'll see that the URL for the service hello-world has been automatically forwarded for you. Cmd + click (or Ctrl + click) on it to get a new tab with the application main page:


  1. Observe how the tab with the service's main page keeps reloading and nothing happens. Navigate back to the Cloud Shell Editor tab, where you'll see that Cloud Code has brought you to the line where you established the breakpoint:


  1. Click on the Continue button to allow the code to continue execution past the breakpoint:


  1. Navigate back to the tab where you were expecting the application main page to load: You will see the service's main page being rendered:


Your application is now running in the Cloud Code local emulator and serving its main page!

  1. As you won't continue debugging, navigate back to Cloud Shell Editor, and remove the breakpoint by clicking on the red dot in line 62 in the main.go file.

Deploying the app on Cloud Run on GCP

As a final step, you will now deploy the application on Cloud Run on GCP:

  1. Go to the Cloud Shell Editor and invoke Cloud Code again by pressing Cmd + p and typing "deploy to cl". The option Cloud Code: Deploy to Cloud Run will show up. Click on it:


  1. A new pane will open called Deploy to Cloud Run where you can configure different service settings and deployment options. Leave all the defaults, scroll down to the end of the page and click on Deploy:


  1. Go to the Output pane at the bottom of Cloud Shell Editor and select Deploy to Cloud Run - Detailed in the upper left of the pane to observe what's going on in Cloud Run on GCP when the application is deploying:


  1. After some time, you will see the service URL from Cloud Run on GCP serving 100% of the traffic for the revision you just deployed and offering you the public service URL for you to test:


  1. Cmd + click on the service URL. A new tab will open with the service main page you just saw in the previous section. This time, the application is serving it from the Cloud Run service running on GCP.

8. Congratulations!

Congratulations, you finished the codelab!

What you've covered

  • Navigated and got familiar with Cloud Shell main features
  • Practiced with different Cloud Shell usage patterns
  • Customized your Cloud Shell environment for advanced use
  • Got familiar with Cloud Code options and features
  • Reviewed the details of Cloud Code for Kubernetes applications
  • Deployed and debugged Containerized applications with Cloud Code on Cloud Shell Editor
  • Use local emulators like Minikube