Cloud Run release notes

New finer-grained predefined IAM roles are available for Cloud Run: Cloud Run Service Invoker, Cloud Run Jobs Executor, Cloud Run Jobs Executor With Overrides. These roles make it easier to grant least privilege access to production accounts accessing Cloud Run resources.

You can now create custom organization policies for Serverless VPC Access connectors and apply them to projects, folders, or organizations (GA).

You can now set a task timeout up to 168 hours (7 days) for Cloud Run jobs. (Preview)

Support for the Go 1.23 runtime is now in Preview.

Support for the Node.js 22 runtime is now in general availability (GA).

Cloud Run is now in scope for International Traffic in Arms Regulations (ITAR).

The in-memory volume type is now generally available (GA) for Cloud Run services and jobs.

You can now specify mount options when you configure Cloud Storage volume mounts for both Cloud Run services and jobs. (In Preview)

GPU support (Preview) is now available in the following region: europe-west4.

You can now create custom organization policies and apply them to projects, folders, or organizations (GA).

You can now deploy and configure a multi-region service from a single gcloud CLI command (in Preview).

Service-level minimum instances are now generally available (GA).

GPU support (Preview) is now available in the following region: asia-southeast1.

The Direct VPC egress feature of Cloud Run now supports Secure Web Proxy.

You can now apply custom constraints for projects that get enforced by organization policies on your Cloud Run services and jobs (in Preview).

Deterministic URLs, which let you predict a Cloud Run service URL before the service is created, is now in general availability (GA).

The following Cloud Run volume types are now generally available (GA):

• Mounting an NFS file share as a volume for Cloud Run services and jobs .
• Mounting a Cloud Storage bucket as a storage volume for Cloud Run services and jobs.

You can now configure traffic routing between Cloud Run and Cloud Run, Google Kubernetes Engine, and Google Compute Engine services using Cloud Service Mesh service routing APIs. Cloud Run also automatically authenticates calls to destination services using service account credentials (In Preview).

Cloud Run is now supported by Sovereign Controls by Partners. The set of packages and features provided by Sovereign Controls by Partners lets you use Cloud Run while meeting digital sovereignty requirements and managing your workloads with data sovereignty guarantees.

You can now configure GPU in your Cloud Run service (Preview).

You can now deploy functions in Cloud Run (Preview). Functions that were created using the Cloud Functions v2 API can now be directly updated in Cloud Run. Note that you must use Google Cloud SDK 489.0.0 version or later if using the gcloud CLI.

Learn more about the different use cases for deploying functions.

Cloud Run now provides security updates for services that are deployed from source when you specify the runtime base image (Preview). Automatic security updates are enabled by default for functions. For details, see Configure automatic base image updates.

You can now disable the default run.app URL for your Cloud Run services (Preview).

Compute flexible committed use discounts are now available for Cloud Run services with CPU always allocated, and Cloud Run jobs. A single flexible commitment covers eligible spend across Compute Engine, GKE, and Cloud Run. For more information, see Committed use discounts.

The following IAM roles are now available in preview:

• Cloud Run Source Developer (roles/run.sourceDeveloper) for deploying a Cloud Run service or job from source.
• Cloud Run Source Viewer (roles/run.sourceViewer) viewing a Cloud Run service or job that is deployed from source.

Uptime checks can now be configured and viewed directly within the Cloud Run "metrics" page.

Cloud Run is now covered by FedRAMP High.

Cloud Run has been added to Google Cloud's Pricing Calculator.

Support for Direct VPC egress, which lets you send traffic directly to a VPC network with no Serverless VPC Access connector required, is now at general availability (GA).

The Direct VPC egress feature of Cloud Run is now supported in all regions.

Direct VPC egress (Preview) is now available in the following additional regions:

• africa-south1
• asia-south1
• asia-southeast2
• australia-southeast2
• europe-central2
• europe-west2
• europe-west6
• europe-west8
• europe-west9
• europe-west10
• me-central1
• me-central2
• southamerica-west1
• us-east5
• us-west2
• us-west3
• us-west8

Cloud Run services can now connect to a Firestore database using integrations (Preview).

Cloud Run services can now connect to Vertex AI to access generative AI models using integrations (Preview).

You can now mount an NFS file share as a volume for Cloud Run services and jobs. (In Preview)

Direct VPC egress now supports Cloud NAT with Public NAT IP addresses (in Preview).

Charts on the metrics dashboard of Cloud Run services now display deployment events.

You can now apply minimum instance configuration at the service level (in Preview).

You can now set and override the deployment service account for Cloud Run integrations when creating, updating, or deleting integrations using the Google Cloud CLI.

The following new region is now available: africa-south1.

The option to update a Serverless VPC Access connector is now available at general availability (GA). This feature allows you to edit the machine (instance) type, as well as the minimum and maximum number of instances.

You can now mount a Cloud Storage bucket as a storage volume for services, and also for Cloud Run jobs.

Direct VPC egress (Preview) is now available in the following additional regions:

• asia-east1
• asia-east2
• asia-northeast2
• asia-south2
• australia-southeast1
• europe-north1
• europe-southwest1
• europe-west12
• europe-west4
• me-west1
• northamerica-northeast1
• northamerica-northeast2
• southamerica-east1
• us-east4
• us-south1
• us-west1
• us-west4

For revisions that have CPU allocation set to CPU always on, instance autoscaling now occurs for CPU activity even outside of incoming requests.

You can now collect Prometheus metrics from Cloud Run services by using the Managed Service for Prometheus sidecar for Cloud Run.

For services with cold start times exceeding 10 seconds, requests are now queued for at least the cold start time before timing out while waiting for instances to start.

Cancelling a currently running job execution is now at general availability (GA).

Deploying sidecar containers to your Cloud Run service is now at general availability (GA). Console UI and CLI are also now available for this feature.

Setting custom audiences on your Cloud Run services is now at general availability (GA).

Job overrides are now at general availability (GA). This feature lets you override the arguments, environment variables, number of tasks, and task timeouts already configured for a job when you execute a job.

Shared VPC ingress is now at general availability (GA). Shared VPC traffic is now considered "internal" for Cloud Run services that are connected to the Shared VPC network.

Long running jobs greater than 1 hour are at general availability (GA).

Cloud Run integrations (Preview) are now available in the following regions:

• asia-northeast1
• asia-northeast2
• asia-south1
• asia-southeast2
• australia-southeast1
• europe-central2
• europe-north1
• europe-west2
• europe-west3
• northamerica-northeast1
• southamerica-east1
• us-east4
• us-west2
• us-west3

The following new region is now available: me-central2.

Cloud Run Operators are available in Cloud Composer.

You can now cancel a currently running job execution. (In Preview.)

The following new region is now available: europe-west10.

You can now send traffic directly to a VPC network with no Serverless VPC Access connector required (Preview).

You can now override the arguments, environment variables, number of tasks, and task timeout already configured for a job when you execute a job. (In Preview)

Long running jobs greater than 1 hour are now supported (in Preview).

You can now create and then configure a Serverless VPC Access connector for your service or job directly from the Create form in the Google Cloud console. (Preview)

Allocating up to 32 GiB of memory and up to 8 CPU to your Cloud Run services is now at general availability (GA).

You can now deploy sidecar containers to your Cloud Run service. (In Preview.)

You can now configure in-memory volumes for your Cloud Run containers. (In Preview.)

Cloud Run integrations (Preview) are now available in asia-east1, europe-west4, us-east1, and us-west1.

Cloud Run services can now connect to Firebase Hosting for custom domains and CDN capabilities, using Integrations (Preview).

CPU allocation recommender now automatically recommends CPU allocation changes based on traffic received by your Cloud Run service over the past month. (In Preview)

Cloud Run integrations (Preview) are now available in europe-west1.

Session affinity for Cloud Run service revisions is now at general availability (GA).

A Cloud Run service revision will now accept requests from the Shared VPC network that it is connected to, including when Ingress is configured as "Internal" or "Internal and Cloud Load Balancing." (Preview)

Startup CPU boost for Cloud Run services is now at general availability (GA).

Support for Identity-aware Proxy (IAP) with Cloud Run to use identity and context to guard access to your applications is now at general availability (GA).

Regional external and regional internal HTTP(S) load balancers now support using Cloud Run services as backends for the load balancer. This is configured using a serverless network endpoint group (NEG).

For details, see:

• Serverless NEG concepts
• Setting up a regional external HTTP(S) load balancer with a Cloud Run backend
• Setting up an internal HTTP(S) load balancer with a Cloud Run backend

This feature is available in General availability.

The following new region is now available: me-central1.

Cloud Run jobs are now at general availability (GA).

The following new region is now available: europe-west12.

Cloud Run healthcheck probes now support container port configuration.

You can now authenticate to a Cloud Run service by including a Google-signed OpenID Connect ID token in the X-Serverless-Authorization header if your application already uses the Authorization header for custom authorization.

You can now deploy public container images from Docker Hub to Cloud Run.

You can now deploy multi-architecture container images to Cloud Run if their manifest list includes amd64/linux.

The option to update a Serverless VPC Access connector is now available in preview. This feature allows you to edit the machine (instance) type, as well as the minimum and maximum number of instances.

Healthcheck probes are now at general availability (GA).

Cloud Run support for a new second generation execution environment is now at generally availability (GA).

Cloud Run support for network file systems such as NFS, NDB, 9P, CIFS/Samba, and Ceph, as well as Cloud Filestore and Cloud Storage FUSE, is now at general availability (GA.)

Logs from Cloud Run services can now be tailed or viewed in a command-line friendly format using gcloud beta run services logs tail and gcloud beta run services logs read

Cloud Run services can now connect to Memorystore for Redis instances using integrations (Preview).

Cloud Run services can now use the Global External HTTP(S) Load Balancer to map Custom Domains using integrations (Preview).

New security recommendations are created for Cloud Run services, which recommends securing environment variables that might contain passwords, API keys and Google application credentials.

The Cloud Run first generation execution environment now has faster filesystem performance.

You can now configure an HTTP liveness healthcheck probe.

Cloud Run now supports workforce identity federation

Startup CPU boost for revisions is now available to provide additional CPU during container instance startup time.

The following new region is now available: me-west1.

You can now deploy Cloud Run services from Cloud Deploy (Preview).

Startup healthcheck probes are now available (Preview).

Cloud Run now supports container images in the Open Container Initiative (OCI) image format.

Cloud Run now writes Access Transparency logs, see Enabling Access Transparency.

Session affinity is now available for Cloud Run service revisions.

The following new region is now available: us-south1.

You can now create and edit Cloud Run jobs using the Cloud console.

The following new region is now available: us-east5.

You can now tag services using Resource Manager tags for fine-grained access control.

Cloud Run jobs are now available in Preview.

The following new region is now available: europe-southwest1.

You can now define service-level objectives (SLOs) for your Cloud Run services using SLO monitoring in Cloud Monitoring or the Cloud Run service page.

The following new region is now available: europe-west9.

You can now allocate up to 32 GiB of memory and up to 8 CPU to your Cloud Run services.

The following new region is now available: europe-west8.

Cloud Run reports a new Cloud Monitoring metric: Container Startup Latency, measuring the startup time of container instances.

Support for Serverless VPC Access connectors in Shared VPC host projects is now at general availability (GA). Learn about the advantages of this method and how to configure connectors in host projects.

Cloud Run now supports using less than one CPU. Refer to CPU limits for details. (Available in public preview.)

BigQuery remote functions allow you to implement custom BigQuery SQL functions leveraging Cloud Run HTTP services (Preview)

The ability to configure Cloud Run services to have CPU allocated for the entire lifetime of container instances is now at general availability (GA).

Internal ingress from Workflows to Cloud Run is now at general availability (GA).

The following new region is now available: southamerica-west1.

Cloud Run support for referencing Secret Manager Secrets is now at general availability (GA).

You can now allocate up to 16GiB of memory to your Cloud Run services.

Committed use discount recommender now automatically generates recommendations to purchase Cloud Run committed use discounts based on historical usage.

Cloud Run now supports network file systems such as NFS, NDB, 9P, CIFS/Samba, and Ceph, as well as Cloud Filestore and Cloud Storage FUSE. (Available in public preview.)

Cloud Run now supports a new second generation execution environment that provides full Linux compatibility rather than system call emulation. This execution environment provides better performance and the ability to use network file systems. (Available in public preview.)

Customer managed encryption keys are now at general availability (GA).

Binary Authorization for Cloud Run is now at generally availability (GA).

You can now configure Cloud Run services to have CPU allocated for the entire lifetime of container instances. Pricing depends on the CPU allocation configuration. (Available in public preview.)

Deploying to Cloud Run from source code is now at General Availability (GA).

The following new region is now available: northamerica-northeast2.

Cloud Run VPC Service Controls are now at General Availability (GA).

Committed use discounts are now at General Availability (GA).

The following organization policies are now at General Availability (GA): Cloud Run Allowed ingress settings and Allowed VPC egress settings.

Cloud Run container instances can now process up to 1,000 concurrent requests, see Setting maximum concurrency. The default is still 80.

Cloud Run is now covered by FedRAMP Moderate

Cloud Run is now available in the following region:

• asia-south2 (Delhi, India)

Cloud Run is now available in the following region:

• australia-southeast2 (Melbourne)

Cloud Run support for WebSockets, HTTP/2, and gRPC streaming are now at general availability (GA).

Request timeouts up to 60 minutes are now at general availability (GA).

User labels now appear in logs.

Committed use discounts are now available for Cloud Run . (Available in public preview.)

Customer managed encryption keys are now available for use with Cloud Run. (Available in public preview.)

You can now use Binary authorization with Cloud Run to enforce policy-based deployment of Cloud Run services. (Available in public preview.)

Recommender now provides recommendations for securing Cloud Run services by creating dedicated service accounts. (Available in public preview.)

Cloud Run now provides UI, command line, and YAML support for referencing Secret Manager Secrets. (Available in public preview.)

You can now use Identity-aware Proxy with Cloud Run to use identity and context to guard access to your applications. (Available in public preview.)

Cloud Run is now available in europe-central2 (Warsaw)

Restricting ingress on Cloud Run is now at general availability (GA).

"Memory limit exceeded" and "No instances available" errors are now captured and aggregated in Cloud Error Reporting

Shared VPC on Cloud Run is now at general availability (GA).

The ability to specify a minimum number of container instances to be kept warm and ready to serve requests is now at general availability (GA).

You can now use VPC Service Controls with Cloud Run to set up a secure perimeter to guard against data exfiltration. (Available in public preview.)

Cloud Run reports a new Cloud Monitoring metric: Instance count, which counts the number of container instances that exist, broken down by state (active or idle).

Cloud Run is now available in the following regions:

• us-west2 (Los Angeles)
• us-west3 (Salt Lake city)
• us-west4 (Las Vegas)

Cloud Run now supports WebSockets, HTTP/2 and gRPC streaming.

Cloud Run now allows you to restrict ingress of your Cloud Run services.

You can now allocate up to 8GiB of memory to your Cloud Run services.

You can now build and deploy source code to Cloud Run using a single command: gcloud beta run deploy --source .

Cloud Run container instances can now process up to 250 concurrent requests, see Configuring maximum concurrency. The default is still 80.

Cloud Run services can now be triggered using Eventarc (available in public preview)

Cloud Run is now available in the following regions:

• asia-east2 (Hong Kong)
• asia-northeast3 (Seoul, South Korea)
• asia-southeast2 (Jakarta)
• asia-south1 (Mumbai, India)
• europe-west2 (London, UK)
• europe-west3 (Frankfurt, Germany)
• europe-west6 (Zurich, Switzerland)
• southamerica-east1 (Sao Paulo, Brazil)

You can now purchase a custom domain via Cloud Domains using the Cloud Run user interface.

You can now specify a minimum number of container instances to be kept warm and ready to serve requests, for services requiring reduced latency and fewer cold starts.

You can now control egress traffic from a service and route all outbound requests to your VPC network. This allows you to configure a static outbound IP address by leveraging Cloud NAT.

You can now allocate 4 vCPUs to container instances of Cloud Run services.

Traces of requests to Cloud Run services are now automatically captured in Cloud Trace

When a container instance needs to be shut down, it now receives a SIGTERM signal. If handled, CPU is allocated for up to 10 seconds before the container is shut down.

Cloud Run now supports request timeouts up to 60 minutes. However, timeouts greater than 15 minutes are a beta feature.

Cloud Run now supports server-side HTTP and gRPC streaming.

Cloud Code IDE extensions now allow you to develop and debug Cloud Run services locally. See Cloud Code for VS Code and Cloud Code for IntelliJ

You can now allocate up to 4GiB of memory to your Cloud Run (fully managed) services.

When setting up Continuous Deployment in the Cloud Run user interface, you can now select a repository that contains Go, Node.js, Python Java or .NET Core code. It will be built using Google Cloud Buildpacks without needing a Dockerfile.

You can now tag Cloud Run revisions. Tagged revisions get a dedicated URL allowing developers to reach these specific revisions without needing to allocate traffic to it.

Cloud Run is now available in asia-southeast1 (Singapore)

Serverless VPC Access support for Shared VPC is now available in Beta.

Cloud Run resources are now available in Cloud Asset Inventory

The Cloud Run user interface now allows you to easily set up Continuous Deployment from Git using Cloud Build

External HTTP(S) Load Balancing is now supported for Cloud Run services via Serverless network endpoint groups.
Notably, this feature allows you to use Cloud CDN and multi-region load balancing.
This feature is available in Beta.

Cloud Run (fully managed) support for connecting to a VPC network with Serverless VPC Access is now at general availability (GA).

Cloud Run is now available in the following regions:

• asia-northeast2 (Osaka)
• australia-southeast1 (Sydney)
• northamerica-northeast1 (Montréal)

The Cloud Run user interface now allows you to copy a Cloud Run service.

Export a Cloud Run service to a YAML file with gcloud run services describe SERVICE --format export

The Cloud Run user interface now allows you to edit the service YAML.

The Cloud Run container instance metadata server now exposes the unique identifier of the container instance and the region of the Cloud Run service

Cloud Run (fully managed) now supports connecting to a VPC network with Serverless VPC Access, in beta.

Cloud Code IDE extensions support Cloud Run. See Cloud Code for VS Code and Cloud Code for IntelliJ

The Cloud Run revision details panel now surfaces build information if the Container Analysis API has been enabled and the container has been built with Cloud Build, as well as source repository information if the container has been built by a Cloud Build Trigger.

Cloud Run (fully managed) now supports deploying container images from Cloud Artifact Registry

Cloud Run (fully managed) now supports rollbacks, gradual rollouts (blue/green deployments), and other traffic migration manipulations between revisions.

Cloud Run is now available in the following regions:

• asia-east1 (Taiwan)
• europe-north1 (Finland)
• europe-west4 (Netherlands)
• us-east4 (Northern Virginia)
• us-west1 (Oregon)

You can now allocate 2 vCPUs to Cloud Run (fully managed) services.

You can now customize the container port on which requests are sent. We still recommend listening on $PORT for better container portability.

Deploy Cloud Run services from a local configuration file with gcloud beta run services replace service.yaml.

Specify custom command and arguments for your deployed containers.

Use custom revision names with the --revision-suffix command line flag.

Cloud Run is now covered by HIPAA Compliance.

The max instances setting feature allows you to set a limit to the total number of container instances that are started up to handle traffic.

The "Metrics" tab on the service detail page now includes a "Billable container instance time" chart, allowing you to better understand how many instances are actively serving traffic for this service.

The "Metrics" tab on the service detail page now includes an "Error Reporting" table that displays the top application errors for this service.

Cloud Run (fully managed) now supports unary gRPC.

Cloud Run (fully managed) v1 API is now available.

You can set labels on Cloud Run services and revisions.

The following new regions are now available: asia-northeast1, europe-west1, and us-east1.

New YAML tab on the service details page.

Per-service identity.

New "Metrics" tab in the Cloud Run service detail view, displaying a list of curated monitoring metrics.

Cloud Run (fully managed) has been added to the Google Cloud Platform Pricing Calculator.

Cloud SQL is now supported.

Cloud Run (fully managed) Beta release.

Cloud Run (fully managed) Alpha release.