Cloud Run release notes

Support for the Go 1.27 runtime is in Preview.

Starting from Go runtime version 1.26 and later, the lifecycle support dates align more closely with the Go community release cycle. For more information, see Runtime support schedule.

Cloud Run NVIDIA L4 GPU driver version 580.x.x is available for services, jobs, and worker pools.

Cloud Run supports sandboxes for all resources, including jobs and worker pools (Preview).

Support for the Node.js 26 runtime is in Preview.

Support for Budget spend caps to pause your Cloud Run workloads is in Preview.

Cloud Run support for importing public container images from GitHub Container Registry is in General Availability.

Cloud Run sandboxes provide a fast and secure isolated environment to execute untrusted code, such as code generated by AI agents. For more information, see Configure sandboxes for services and Code execution in Cloud Run (Preview).

Deploy a highly available, multi-region Cloud Run service with automated failover and failback for internal and external traffic using Cloud Run service health in General Availability (GA).

Configure HTTP and gRPC readiness probes for your Cloud Run services is in General Availability (GA).

Cloud Run ephemeral disk, which allows you to mount a volume that persists only for the duration of your service, job, or worker pool instance, is in Preview.

Support for specifying custom CPU or concurrency targets using scaling controls is in Preview.

The Cloud Run remote MCP server, which lets agents and AI applications deploy with Cloud Run, is in General Availability (GA).

Support for worker pools is in General Availability (GA).

Support for NVIDIA RTX PRO 6000 Blackwell GPU is in General Availability. For more information, see GPU support for services, jobs, and worker pools.

Deploying services using a Compose file is in General Availability.

Support for Ruby 4.0 runtime is in General Availability.

Configuring Identity-Aware Proxy (IAP) directly on Cloud Run to secure your services without the need for load balancers is in General Availability (GA).

Support for Go 1.26 runtime is in General Availability.

Support for Ruby 4.0 runtime is in Preview.

Support for PHP 8.5 runtime is in General Availability.

Deploy a highly available, multi-region Cloud Run service with automated failover and failback for external traffic using Cloud Run service health (Preview).

You can use the Cloud Run remote MCP server to let agents and AI applications deploy with Cloud Run (Preview).

Support for Go 1.26 runtime is in Preview.

Support for .NET 10 runtime is in General Availability.

Cloud Run source deployment supports Ubuntu 24 LTS base images in General Availability. This builder is available under gcr.io/buildpacks/builder:google-24. For more information, see Builders.

Support for osonly24 runtime is in General Availability. The OS only runtime lets you deploy binaries such as Dart and Go. For more information, see Configure the OS only runtime.

Expanded coverage for compute flexible committed use discounts (CUDs) is available to all Cloud Billing accounts. Your Cloud Billing accounts have been automatically migrated to the new spend-based CUD model and you no longer need to opt-in to benefit from the expanded coverage. For the full list of eligible SKUs across Compute Engine, GKE, and Cloud Run, see SKU Groups - Compute Flexible CUD Eligible SKUs.

To learn more about compute flexible CUDs for Cloud Run and how they apply to your usage, see the compute flexible CUDs documentation.

You can configure Direct VPC ingress for Cloud Run worker pools. When you configure Direct VPC ingress, each worker instance receives a private IP address on your configured network and subnet. To access private IP addresses between instances in your VPC network for secure internal communication, see Retrieve the private IP addresses using the metadata server (MDS). 

Support for NVIDIA RTX PRO 6000 Blackwell GPU is in Preview. For more information, see GPU support for services, jobs, and worker pools.

Support for PHP 8.5 runtime is in Preview.

Support for .NET 10 runtime is in Preview.

The Python buildpack supports default entrypoint detection for the Agent Development Kit (ADK) framework in General Availability. For more information, see Build a Python application.

The following new region is now available: asia-southeast3.

Cloud Run and Cloud Run functions source deployments support the pyproject.toml file for managing dependencies. This feature is in General Availability for all supported Python versions. For more information, see Deploy Python applications with a pyproject.toml file.

Support for Java 25 runtime is in General Availability.

Support for Python 3.14 runtime is in General Availability. Starting from Python version 3.14 and later, the Python buildpack uses the uv package manager as the default installer for the dependencies you specify in your requirements.txt file. You can also use pip as the default installer for these versions by setting the GOOGLE_PYTHON_PACKAGE_MANAGER environment variable to pip. For more information, see Specify dependencies in Python.

Cloud Run and Cloud Run functions source deployments support pyproject.toml file for managing dependencies. This feature is in General Availability for Python version 3.13 and later, and is in Preview for Python version 3.12 and earlier. For more information, see Deploy Python applications with a pyproject.toml file.

The Python buildpack supports default entrypoint detection for the Agent Development Kit (ADK) framework (Preview). For more information, see Build a Python application.

Support for osonly24 runtime is in Preview. The OS only runtime lets you deploy Go applications from source, and binaries such as Dart and Go. For more information, see Configure the OS only runtime.

You can use Developer Connect in the Cloud Run console to set up continuous deployments from GitHub, GitLab, and Bitbucket repositories (Preview).

Deploy a highly available, multi-region Cloud Run service with automated failover and failback for internal traffic using Cloud Run service health (Preview).

Configure HTTP and gRPC readiness probes for your Cloud Run services (Preview).

Support for Node.js 24 runtime is in General Availability.

You can deploy source artifacts directly to Cloud Run, bypassing the Cloud Build step. (Preview)

Cloud Run and Cloud Run functions source deployments support pyproject.toml file for managing dependencies. If you use a pyproject.toml file, source deployments use one of the following to find and install dependencies:

• pip
• uv
• poetry

For more information, see Deploy Python applications with a pyproject.toml file (Preview).

The time it takes for initial deployments to Cloud Run in a new project has been reduced. This change results in reduced latency and a faster getting started experience.

You can deploy services to Cloud Run using a Compose file (Preview).

Support for Python 3.14 runtime is in Preview. Starting from Python version 3.14 and later, the Python buildpack uses the uv package manager as the default installer for the dependencies you specify in your requirements.txt file. You can also use pip as the default installer for these versions by setting the GOOGLE_PYTHON_PACKAGE_MANAGER environment variable to pip. For more information, see Specify dependencies in Python.

Cloud Run source deployment supports Ubuntu 24 LTS base images (Preview). This builder is available under gcr.io/buildpacks/builder:google-24. For more information, see Builders.

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

Use dual-stack subnets with IPv6 to let your Cloud Run resources send IPv4 and internal IPv6 traffic to a VPC network with Direct VPC egress, and send external IPv6 traffic to the public internet. (GA)

Support for Java 25 runtime is in Preview.

For Cloud Run source deployed services and functions with GPU enabled, Cloud Run defaults to using Cloud Build's e2-highcpu-8 machine type for the build process when using the gcloud CLI or the Google Cloud console. This change allows for higher CPU support and faster build times, and also leads to a moderate increase in the overall cost of your service (GA).

Support for configuring GPU for your Cloud Run job is in General Availability (GA).

Direct VPC egress now supports Private NAT (GA).

Direct VPC egress now supports VPC Flow Logs (Preview).

Support for applying maximum instance configuration at the service level is in General Availability (GA).

Support for setting multiple environment variables using the .env file is in General Availability (GA). For more information, see Configure environment variables for services, jobs, and worker pools.

You can specify mount options when you configure Cloud Storage volume mounts for Cloud Run services, jobs, and worker pools. (GA)

You can deploy and configure a multi-region service from a single gcloud CLI command or by using a YAML or Terraform file (GA).

Cloud Run Threat Detection is available in General Availability.

You can configure GPU in your Cloud Run worker pool (Preview).

Support for Go 1.25 runtime is in General Availability (GA).

For Cloud Run source deployed services and functions with GPU enabled, Cloud Run defaults to using Cloud Build's e2-highcpu-8 machine type for the build process when you use the gcloud beta run command (Preview). This change allows for higher CPU support and faster build times, and also leads to a moderate increase in the overall cost of your service.

The Python buildpack supports Cloud Run source deployments for modern web frameworks such as FastAPI, Gradio, and Streamlit.

For Python version 3.13 and later, the Python buildpack sets the default entrypoint for Cloud Run source deployments based on the web server or framework configuration in your requirements.txt file. For more information, see Build a Python application.

You can set multiple environment variables using the .env file (Preview). For more information, see Configure environment variables for services, jobs, and worker pools.

Support for manually scaling your Cloud Run service is now at General Availability (GA).

Support for Go 1.24 runtime is in General Availability (GA).

Support for Go 1.25 runtime is in Preview. This runtime is available for early testers using existing release candidates.

Support for Node.js 24 runtime is in Preview. Node.js 24 is in the Current release state and enters long-term support (LTS) in October 2025. For more information, see Node.js v24.0.0 (Current) in the Node.js website.

You can disable the built-in run.app URL of a Cloud Run service to ensure that traffic can only ingress through paths that you've explicitly configured (GA).

Support for the Go 1.24 runtime is in Preview.

Compute flexible committed use discounts (CUDs) have expanded to also cover your Cloud Billing account's spend across Cloud Run services with request-based billing and Cloud Run functions.

The improved spend-based CUD experience is available without requiring an opt-in for new users or users who don't have an active spend-based CUD.

To learn more about how opting into the new model affects your flexible CUDs, see Committed use discounts.

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

Cloud Run worker pools are now available (Preview). Worker pools are specifically designed for non-request workloads.

A new region is now available for Cloud Run GPUs: us-east4.

Support for the PHP 8.4 runtime is in General Availability (GA).

Support for the Ruby 3.4 runtime is in General Availability (GA).

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

You can use request host and request path in IAM Conditions when defining access control for invoking Cloud Run services.

For Java Cloud Run functions that use functions-framework version 1.4.0 or later, you can now use the logging class java.util.logging.Logger to add a unique execution ID to log outputs.

Multiple regions now benefit from enhanced responsiveness for latency-sensitive applications for Cloud Run service URLs.

The region selector when creating a service or a job from the Google Cloud console now defaults to europe-west1.

Labels you previously set for your Cloud Run functions using either gcloud functions commands or the Cloud Functions v2 API propagate to Cloud Run when you deploy your functions in Cloud Run. For more information on creating labels in Cloud Run, see Configure labels for services.

Direct VPC egress supports Private NAT (Preview).

The Cloud Monitoring memory usage metrics now show lower memory utilization for most services using the second generation execution environment. These metrics previously included memory used by the operating system page cache.

Support for the Ruby 3.4 runtime is in Preview.

Support for the Python 3.13 runtime is in General Availability (GA).

Support for the PHP 8.4 runtime is in Preview.

Cloud KMS with Autokey is now in General Availability (GA) for Cloud Run.

Support for the Python 3.13 runtime is now in Preview.

Gemini Cloud Assist in Cloud Run is supported in Preview. You can use the chat panel to design, optimize, and troubleshoot your Cloud Run apps with Gemini assistance.

Direct VPC egress support for Cloud Run jobs is now generally available (GA).

You can now configure Identity-Aware Proxy (IAP) for Cloud Run to secure your services with a single click from all ingress paths (in Preview).

Configuring GPU in your Cloud Run service is now generally available (GA).

Cloud Run Threat Detection is available in Preview.

Deploying multiple containers (sidecars) to a Cloud Run job is now generally available. (GA)

The ability to disable the Invoker IAM check for Cloud Run services is now at general availability (GA).

Cloud Run services configured with Direct VPC egress now use only 2 times (2X) as many IP addresses as the number of instances for the duration of the instance plus up to 20 minutes, reduced from 4X as many IP addresses.

New services using GPUs by default will have zonal redundancy turned on. However, you can now specify GPUs with zonal redundancy or without zonal redundancy, and request quota for either of these configurations. (In Preview)

A new region is now available for Cloud Run GPUs: europe-west1.

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

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

Support for the Go 1.23 runtime is now in general availability (GA).

Support for deploying functions in Cloud Run is now in general availability (GA). Note that you must use Google Cloud SDK 511.0.0 version or later if using the gcloud CLI. Review the use cases guide for deploying new functions.

Support for configuring automatic base image updates for Cloud Run source deployed services and functions is now in general availability (GA). Note that you must use Google Cloud SDK 511.0.0 version or later if using the gcloud CLI.

You can now scale your Cloud Run service manually, in place of the built-in Cloud Run autoscaling feature. (Preview)

Cloud Run integrations are discontinued from the Google Cloud console and Google Cloud CLI. No action is required; your deployed services that use these integrations will continue to work. We recommend transitioning to use the individual product experiences for each integration you have deployed. For more information about configuring resources for your services to connect to other Google Cloud products, see Connect to Google Cloud services.

When deploying a function in Cloud Run, you can now specify an Artifact Registry image repository to store the container (Preview).

You can now use dual-stack subnets with internal IPv6 to let your Cloud Run services and jobs send IPv4 and internal IPv6 traffic to a VPC network with Direct VPC egress. (Preview)

The Cloud Run Builder (roles/run.builder) IAM role is now available in preview. When deploying a service or function from source, grant this role to the Compute Engine default service account that builds your Cloud Run resource.

You can now deploy multiple containers (sidecars) to a Cloud Run job. (In Preview)

The principal (user or service account) creating or updating a Cloud Run resource now needs explicit permission to access the container image(s). When using Artifact Registry, ensure the principal has the Artifact Registry Reader (roles/artifactregistry.reader) IAM role on the project or repository containing the container image(s) to deploy.

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.

Service-level minimum instances are now set using the --min command line flag, --service-min-instances remains available as an alias to --min.

The CPU allocation setting has been renamed to Billing in the Google Cloud console for Cloud Run services.

The two billing settings are:

• Request-based billing (default), previously called CPU is only allocated during request processing, only charges your Cloud Run instances during request processing, container startup, and container shutdown.
• Instance-based billing, previously called CPU always allocated, charges your Cloud Run instances for the entire lifecycle of instances, even when there are no incoming requests.

For more details, see the Billing settings guide.

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).

asia-south1 (Mumbai, India) is now subject to Tier 1 pricing.

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).

Cloud Run integrations are discontinued from the Google Cloud console and Google Cloud CLI for new users. If you are an existing user, you will continue to have access until January 2025. No action is required, your deployed services that use these integrations will continue to work. We recommend transitioning to use the individual product experiences for each integration you have deployed. For more information about configuring resources for your services to connect to other Google Cloud products, see Connect to Google Cloud services.

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 runtime support schedule for some PHP runtimes has been extended to match PHP's public support schedule.

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.

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 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.

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.

Starting July 2024, Cloud Build changed the default behavior for how Cloud Build uses service accounts in new projects. This change is detailed in Cloud Build Service Account Change documentation. As a result of this change, new projects deploying to Cloud Run from source code for the first time may be using a default Cloud Build service account with insufficient permissions for deploying from source.

If you are impacted by this change, you can do one of the following:

• Review the Cloud Build guidance on changes to the default service account and opt out of these changes.
• Grant the Cloud Build Service Account (roles/cloudbuild.builds.builder) role to the Compute Engine default service account.

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.

All jobs are now subject to maintenance events, not just jobs longer than one hour, which increases reliability for jobs under 1 hour. These maintenance events are transparent and don't require any changes to your container.

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 Vertex AI to access generative AI models using integrations (Preview).

Cloud Run services can now connect to a Firestore database 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

Tags configured on Cloud Run services are now available when exporting Cloud Billing data to BigQuery.

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)

Accessing a service that's prohibited by the Internal or Internal and Cloud Load Balancing ingress setting now results in a 404 rather than 403 error code.

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).

Cloud Run now logs container health check failures, including default TCP startup probe failures.

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 source deployment now supports Ubuntu 22 LTS base images. This is a new builder that is available under gcr.io/buildpacks/builder:google-22 and addresses multiple security issues. You can read more about the google-22 builder in our announcement on GitHub.

The default builder for Cloud Run source deployments will be switched to google-22 at a future date. To preview the google-22 builder, see Deploy from source with Cloud Run.

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).

Source code deployments that use Node.js now automatically run the npm run build command by default when any build script is defined in the package.json file.

For details about how to configure the package.json file, including the option to set environment variables or prevent the default script from running, see the Node.js buildpack configuration in the Google Cloud's buildpacks documentation.

When deploying a new revision, Cloud Run now starts enough instances of the new revision before directing traffic to it. This reduces the impact of new revision deployments on request latencies, notably when serving high levels of traffic.

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.

When session affinity is enabled on a Cloud Run service that is splitting traffic between multiple revisions, requests from the same clients are now routed to the same revision. When updating the traffic splitting configuration, Cloud Run minimizes the number of clients that are redirected to a new revision.

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.

Terraform resources for Cloud Run Services and Cloud Run Jobs based on the Cloud Run Admin API v2 are now generally available (GA).

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 use the Global External HTTP(S) Load Balancer to map Custom Domains using integrations (Preview).

Cloud Run services can now connect to Memorystore for Redis instances 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 Admin API v2 is now at general availability (GA).

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.