Overview

In this exercise, you deploy a Cloud Run service and use Eventarc to receive events from Pub/Sub. In the second part of the lab, you do the same on an Anthos GKE cluster with the Cloud Run for Anthos offering.

Objectives

In this lab, you learn how to:

• Deploy an event receiver service to Cloud Run and Cloud Run for Anthos.
• Create an event trigger with Eventarc.
• Publish a message to a Pub/Sub topic to generate an event, and view it in the Cloud Run and Cloud Run for Anthos logs.

Setup and requirements

For each lab, you get a new Google Cloud project and set of resources for a fixed time at no cost.

1. Sign in to Google Skills using an incognito window.

2. Note the lab's access time (for example, 1:15:00), and make sure you can finish within that time. There is no pause feature. You can restart if needed, but you have to start at the beginning.

3. When ready, click Start lab.

4. Note your lab credentials (Username and Password). You will use them to sign in to the Google Cloud Console.

5. Click Open Google Console.

6. Click Use another account and copy/paste credentials for this lab into the prompts. If you use other credentials, you'll receive errors or incur charges.

7. Accept the terms and skip the recovery resource page.

Task 1. Review your Anthos GKE cluster and install Cloud Run for Anthos

In this task, you review and prepare the already created Anthos GKE cluster to execute Cloud Run for Anthos. First, you verify that the GKE cluster has been registered in an Anthos Fleet. Second, you confirm that Anthos Service Mesh has been installed in the cluster as a prerequisite to installing Cloud Run for Anthos. Third, you enable and install Cloud Run for Anthos in the cluster.

1. In the Google Cloud Console, on the Navigation menu (), click Kubernetes Engine > Clusters. Notice that a new GKE cluster has been created.

2. Click Workloads, and verify that the cluster is running the Anthos Service Mesh components istio-ingressgateway and istiod-asm.

3. On the Navigation menu, click Anthos > Clusters, and then verify that the cluster has been registered and appears in the list of Anthos managed clusters.

4. Click Activate Cloud Shell (). If prompted click Continue.

5. In Cloud Shell, set the Zone environment variable:

   C1_ZONE={{{ project_0.default_zone| "Zone added at lab start" }}}

6. In Cloud Shell, initialize the environment variables:

7. Get the credentials for your gke GKE cluster:

8. Enable Cloud Run for Anthos on your project:

9. Enable the Eventarc APIs:

10. Install Cloud Run for Anthos on your cluster:

If this step fails, wait 30 seconds and try again.

Task 2. Deploy a Cloud Run application

1. In Cloud Shell, clone the repository:

2. Build the container and upload it to Cloud Build:

3. Deploy the container image to Cloud Run:

4. If asked to enable the API, type y.

When the service URL is displayed, the deployment is complete.

Task 3. Create an Eventarc trigger for Cloud Run

When a message is published to the Pub/Sub topic, the event trigger sends messages to the event receiver service deployed on Cloud Run.

1. In Cloud Shell, create a trigger to listen for Pub/Sub messages:

This creates a new Pub/Sub topic and a trigger for it called events-pubsub-trigger. The Pub/Sub subscription persists regardless of activity and does not expire.

2. Confirm that the trigger was successfully created:

3. Find and set the Pub/Sub topic as an environment variable:

4. Send a message to the Pub/Sub topic to generate an event:

The event is sent to the Cloud Run service, which logs the event message.

5. To view the event message, in the Google Cloud Console, navigate to Cloud Run.

6. Click on the helloworld-events-pubsub-tutorial service.

7. On the Logs tab, look for the "Hello, Runner!" message.

Congratulations! You deployed a Cloud Run application and used Eventarc to trigger events from Pub/Sub.

Task 4. Prepare the environment for Eventarc and Cloud Run for Anthos

1. Create a service account to use when creating triggers:

2. Grant appropriate roles to the new service account:

3. Enable GKE destinations for Eventarc:

4. At the prompt to bind the required roles, type y.

The following roles are bound:

• roles/compute.viewer
• roles/container.developer
• roles/iam.serviceAccountAdmin

Task 5. Deploy the Cloud Run for Anthos application

• Deploy the container image to Cloud Run for Anthos:

  gcloud run deploy subscriber-service \ --cluster $C1_NAME \ --cluster-location $C1_ZONE \ --platform gke \ --image gcr.io/$(gcloud config get-value project)/events-pubsub

  If the command fails, the Anthos GKE cluster is not yet ready to accept Cloud Run for Anthos services. Wait a couple of minutes and try again.

Task 6. Create an Eventarc trigger for Cloud Run on Anthos

1. In Cloud Shell, create a trigger to listen for Pub/Sub messages:

This creates a new Pub/Sub topic and a trigger for it called pubsub-trigger. The Pub/Sub subscription persists regardless of activity and does not expire.

2. Confirm that the trigger was successfully created:

3. Find and set the Pub/Sub topic as an environment variable:

4. Send a message to the Pub/Sub topic to generate an event:

The event is sent to the Cloud Run for Anthos service, which logs the event message.

5. To view the event message in the service logs, on the Navigation menu, click Kubernetes Engine > Applications.

6. Click on Go to List of Services.

7. Click on the subscriber-service.

8. On the Logs tab, look for the "Hello, Cloud Run on Anthos!" message.

Congratulations! You deployed a Cloud Run for Anthos application and used Eventarct to trigger events from Pub/Sub.

End your lab

When you have completed your lab, click End Lab. Google Skills removes the resources you’ve used and cleans the account for you.

You will be given an opportunity to rate the lab experience. Select the applicable number of stars, type a comment, and then click Submit.

The number of stars indicates the following:

• 1 star = Very dissatisfied
• 2 stars = Dissatisfied
• 3 stars = Neutral
• 4 stars = Satisfied
• 5 stars = Very satisfied

You can close the dialog box if you don't want to provide feedback.

For feedback, suggestions, or corrections, please use the Support tab.

Copyright 2026 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.