Configure Cloud Run in Application Design Center

Cloud Run is a fully managed application platform that lets you run containers directly on top of Google's scalable infrastructure. For more information, see Cloud Run overview .

This document describes the connections and parameters you can configure when using App Design Center to create a Cloud Run service. The configuration parameters are based on the terraform-google-cloud-run Terraform module.

Component connections

The following table includes the components that you can connect to a Cloud Run service, and the resulting updates to your application and its generated Terraform code.

Connected component

Application updates

Background information

  • The Cloud Run service can reference the secret data.
  • The Secret Manager Secret Datafield is referenced by the Cloud Run env_secret_vars field.
  • The roles/secretmanager.secretAccessor role is added to the Cloud Run service account.
  • The Cloud Run service uses the service account as a service identity .
  • The roles/run.invoker role is added to the service account.
  • The service account email and IAM information are added to the Cloud Run environment variables.
  • The Cloud Run service can connect to the AlloyDB for PostgreSQL instance.
  • The AlloyDB for PostgreSQL resource metadata is added to the Cloud Run environment variables.
  • The AlloyDB for PostgreSQL roles/alloydb.admin role is added to the Cloud Run service account.
  • The Cloud Run service can interact with the BigQuery dataset.
  • The BigQuery resource metadata is added to the Cloud Run environment variables.
  • The BigQuery roles/bigquery.dataEditor role is added to the Cloud Run service account.
  • The Cloud Run service can perform administrative functions on the Bigtable instance.
  • The Bigtable resource metadata information is added to the Cloud Run environment variables.
  • The roles/bigtable.admin role is added to the Cloud Run service account.

Another Cloud Run service

  • The source Cloud Run service can send traffic to the destination Cloud Run service.
  • The source Cloud Run service contains the destination Cloud Run service URI in its environment variables.
  • The Cloud Run service can read and write data to the Cloud SQL (MySQL) instance.
  • The Cloud SQL connection metadata is added to the Cloud Run service.
  • The roles/cloudsql.instanceUser and roles/cloudsql.client roles are added to the Cloud Run service account.
  • The Cloud Run service account is added as an IAM user to the Cloud SQL instance.
  • The Cloud Run service can read and write data to the Cloud SQL (PostgreSQL) instance.
  • The Cloud SQL connection metadata is added to the Cloud Run service.
  • The roles/cloudsql.instanceUser and roles/cloudsql.client roles are added to the Cloud Run service account.
  • The Cloud Run service account is added as an IAM user to the Cloud SQL instance.
  • The Cloud Run service can manage objects in the Cloud Storage bucket.
  • The Cloud Run service account IAM information is added to the Cloud Storage bucket.
  • The roles/storage.objectAdmin role is assigned to the Cloud Run service account.
  • The load balancer can distribute incoming traffic to the Cloud Run service.
  • The Cloud Run service is added as a backend endpoint in the Cloud Load Balancing serverless NEG backends configuration.
  • The Cloud Run service can cache data in the Memorystore for Redis instance.
  • The Memorystore for Redis connection information is added to the Cloud Run environment variables.
  • The roles/redis.editor role is added to the Cloud Run service account.
  • The Cloud Run service can receive messages or publish to the Pub/Sub topic.
  • The Pub/Sub topic ID is added to the Cloud Run environment variables.
  • The roles/pubsub.publisher and roles/pubsub.subscriber roles are added to the Cloud Run service account.
  • The Cloud Run service is added to the Pub/Sub push and pull subscription fields.
  • The load balancer can distribute incoming traffic to the Cloud Run service.
  • The Cloud Run service is added as a backend endpoint in the Cloud Load Balancing serverless NEG backends configuration.
  • The HTTP and HTTPS IP addresses of the load balancer are available to the application running in the Cloud Run container.
  • The Cloud Load Balancing address metadata is added to the Cloud Run environment variables.
  • The Cloud Run service can manage the Spanner instance.
  • The Spanner connection details are added to the Cloud Run environment variables.
  • The roles/spanner.databaseAdmin role is added to the Cloud Run service account.
  • The Cloud Run service account IAM information is added to the Spanner instance.
  • The Cloud Run service can interact with Vertex AI services.
  • The roles/aiplatform.user role is added to the Cloud Run service account.

Required configuration parameters

If your template includes a Cloud Run component, you must configure the following parameters before you deploy.

Parameter name

Description and constraints

Background information

Project ID

The project where you want to deploy the Cloud Run resource.

Configure components

Region

The Cloud Run service deployment location.

Cloud Run locations

Service Name

name Cloud Run service

Optional configuration parameters

The following parameters are optional. To display advanced parameters, in the Configurationarea, select Show advanced fields.

Feature

Subfeature

Parameter name

Description and constraint information

Background information

Containers

Container Name

Working Dir

The container's working directory. If not specified, the container runtime's default is used, which might be configured in the container image.

Env Secret Vars

Key

Volume Mounts

Name

CPU Idle

Whether CPU is only allocated during requests.

Initial Delay Seconds

HTTP Get Path

HTTP Get Port

HTTP Headers Name

HTTP Headers Value

GRPC Service

Liveness Probe

Create Service Account

Create a new service account for the Cloud Run service.

Service Account Project Roles

Roles to grant to the newly created service account. Enable Create Service Accountand don't provide input for Service Account.

Members

Users and service accounts that can invoke the service. For public access, enter allUsers . For access by logged-in Google users, enter allAuthenticatedUsers , or enter a list of specific users and service accounts. For more information, see members .

VPC Access

Connector

Network Interfaces

Network

Cloud Run Deletion Protection

Prevents Terraform from destroying or recreating Cloud Run jobs and services.

Enable Prometheus Sidecar

Enable Promethus sidecar in the Cloud Run instance.

Default Mode
Cloud SQL Instance
Instances

Service Scaling

Min Instance Count

Template Scaling

Min Instance Count

Service Annotations

Key

Client

Name

Arbitrary identifier for the API client.

Version

Arbitrary identifier for the version identifier.

Binary Authorization

Breakglass Justification

Template Annotations

Key

Create a Mobile Website
View Site in Mobile | Classic
Share by: