Skip to content

anthos.md

Latest commit

 

History

History
81 lines (59 loc) · 1.74 KB

anthos.md

File metadata and controls

81 lines (59 loc) · 1.74 KB

Events for Cloud Run on Anthos – Pub/Sub tutorial

This sample shows how to create a service that processes Pub/Sub events. We assume that you have a GKE cluster created with Events for Cloud Run enabled.

Setup

Login to gcloud:

gcloud auth login

Configure project id:

gcloud config set project [PROJECT-ID]

Configure environment variables:

MY_RUN_SERVICE=pubsub-service
MY_RUN_CONTAINER=pubsub-container
MY_TOPIC=pubsub-topic
MY_PUBSUB_TRIGGER=pubsub-trigger
MY_CLUSTER_NAME=events-cluster
MY_CLUSTER_LOCATION=us-central1-c

Quickstart

Set cluster name, location and platform:

gcloud config set run/cluster ${MY_CLUSTER_NAME}
gcloud config set run/cluster_location ${MY_CLUSTER_LOCATION}
gcloud config set run/platform gke

Deploy your Cloud Run service:

gcloud builds submit \
 --tag gcr.io/$(gcloud config get-value project)/$MY_RUN_CONTAINER
gcloud run deploy $MY_RUN_SERVICE \
 --image gcr.io/$(gcloud config get-value project)/$MY_RUN_CONTAINER

Create a Cloud Pub/Sub topic:

gcloud pubsub topics create $MY_TOPIC

Create a Cloud Pub/Sub trigger:

gcloud alpha events triggers create $MY_PUBSUB_TRIGGER \
--source CloudPubSubSource \
--target-service $MY_RUN_SERVICE \
--type com.google.cloud.pubsub.topic.publish \
--parameters topic=$MY_TOPIC

Test

Test your Cloud Run service by publishing a message to the topic:

gcloud pubsub topics publish $MY_TOPIC --message="John Doe"

You may observe the Cloud Run service printing upon receiving an event in Cloud Logging.

gcloud logging read "resource.type=cloud_run_revision AND \
resource.labels.service_name=$MY_RUN_SERVICE" --project \
$(gcloud config get-value project) --limit 30 --format 'value(textPayload)'