You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
December 01, 2025
You can use Developer Connect in the Cloud Run console to set up continuous deployments from GitHub, GitLab, and Bitbucket repositories (Preview).
November 21, 2025
Configure HTTP and gRPC readiness probes for your Cloud Run services (Preview).
Deploy a highly available, multi-region Cloud Run service with automated failover and failback for internal traffic using Cloud Run service health (Preview).
November 20, 2025
Support for Node.js 24 runtime is in General Availability.
November 19, 2025
You can deploy source artifacts directly to Cloud Run, bypassing the Cloud Build step. (Preview)
November 17, 2025
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.
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:
pipuvpoetry
For more information, see Deploy Python applications with a pyproject.toml
file (Preview).
November 13, 2025
You can deploy services to Cloud Run using a Compose file (Preview).
November 12, 2025
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.
November 11, 2025
You can set a task timeout up to 168 hours (7 days) for Cloud Run jobs. (GA)
November 06, 2025
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)
October 31, 2025
Support for Java 25 runtime is in Preview.
October 30, 2025
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).
October 21, 2025
Support for configuring GPU for your Cloud Run job is in General Availability (GA).
Direct VPC egress now supports Private NAT (GA).
October 20, 2025
Direct VPC egress now supports VPC Flow Logs (Preview).
October 06, 2025
Support for applying maximum instance configuration at the service level is in General Availability (GA).
March 28, 2025
The ability to disable the Invoker IAM check for Cloud Run services is now at general availability (GA).
March 26, 2025
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.
March 25, 2025
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)
March 11, 2025
A new region is now available for Cloud Run GPUs: europe-west1.
March 06, 2025
The following new region is now available: europe-north2.
March 04, 2025
The following new region is now available: northamerica-south1.
March 03, 2025
Support for the Go 1.23 runtime is now in general availability (GA).
February 19, 2025
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.
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.
February 18, 2025
You can now scale your Cloud Run service manually, in place of the built-in Cloud Run autoscaling feature. (Preview)
February 07, 2025
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.
February 04, 2025
When deploying a function in Cloud Run, you can now specify an Artifact Registry image repository to store the container (Preview).
January 24, 2025
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)
January 22, 2025
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.
January 14, 2025
You can now deploy multiple containers (sidecars) to a Cloud Run job. (In Preview)
January 13, 2025
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.
December 17, 2024
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.
December 16, 2024
Service-level minimum instances are now set using the --min command line flag, --service-min-instances remains available as an alias to --min.
December 13, 2024
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.
December 09, 2024
You can now create custom organization policies for Serverless VPC Access connectors and apply them to projects, folders, or organizations (GA).
November 25, 2024
You can now set a task timeout up to 168 hours (7 days) for Cloud Run jobs. (Preview)
November 19, 2024
Support for the Go 1.23 runtime is now in Preview.
November 18, 2024
Support for the Node.js 22 runtime is now in general availability (GA).
November 15, 2024
Cloud Run is now in scope for International Traffic in Arms Regulations (ITAR).
asia-south1 (Mumbai, India) is now subject to Tier 1 pricing.
November 12, 2024
November 07, 2024
October 23, 2024
GPU support (Preview) is now available in the following region: europe-west4.
October 21, 2024
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.
October 10, 2024
You can now deploy and configure a multi-region service from a single gcloud CLI command (in Preview).
October 01, 2024
Service-level minimum instances are now generally available (GA).
June 27, 2024
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.
May 20, 2024
Uptime checks can now be configured and viewed directly within the Cloud Run "metrics" page.
May 17, 2024
Cloud Run is now covered by FedRAMP High.
May 15, 2024
Cloud Run has been added to Google Cloud's Pricing Calculator.
April 24, 2024
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).
April 15, 2024
The Direct VPC egress feature of Cloud Run is now supported in all regions.
March 28, 2024
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.
March 22, 2024
Direct VPC egress (Preview) is now available in the following additional regions:
africa-south1asia-south1asia-southeast2australia-southeast2europe-central2europe-west2europe-west6europe-west8europe-west9europe-west10me-central1me-central2southamerica-west1us-east5us-west2us-west3us-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).
March 19, 2024
March 14, 2024
Direct VPC egress now supports Cloud NAT with Public NAT IP addresses (in Preview).
March 07, 2024
Charts on the metrics dashboard of Cloud Run services now display deployment events.
March 05, 2024
You can now apply minimum instance configuration at the service level (in Preview).
February 13, 2024
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.
January 31, 2024
The following new region is now available: africa-south1.
January 23, 2024
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.
January 19, 2024
You can now mount a Cloud Storage bucket as a storage volume for services, and also for Cloud Run jobs.
January 18, 2024
Direct VPC egress (Preview) is now available in the following additional regions:
asia-east1asia-east2asia-northeast2asia-south2australia-southeast1europe-north1europe-southwest1europe-west12europe-west4me-west1northamerica-northeast1northamerica-northeast2southamerica-east1us-east4us-south1us-west1us-west4
January 10, 2024
Tags configured on Cloud Run services are now available when exporting Cloud Billing data to BigQuery.
September 28, 2021
Customer managed encryption keys are now at general availability (GA).
Binary Authorization for Cloud Run is now at generally availability (GA).
September 13, 2021
August 24, 2021
Deploying to Cloud Run from source code is now at General Availability (GA).
August 03, 2021
The following new region is now available: northamerica-northeast2.
July 27, 2021
Committed use discounts are now at General Availability (GA).
Cloud Run VPC Service Controls 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.
July 26, 2021
Cloud Run container instances can now process up to 1,000 concurrent requests, see Setting maximum concurrency. The default is still 80.
July 20, 2021
Cloud Run is now covered by FedRAMP Moderate
March 31, 2021
"Memory limit exceeded" and "No instances available" errors are now captured and aggregated in Cloud Error Reporting
March 18, 2021
Shared VPC on Cloud Run is now at general availability (GA).
March 08, 2021
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).
March 05, 2021
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.)
March 03, 2021
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).
March 01, 2021
Cloud Run is now available in the following regions:
us-west2(Los Angeles)us-west3(Salt Lake city)us-west4(Las Vegas)
January 20, 2021
Cloud Run now supports WebSockets, HTTP/2 and gRPC streaming.
December 18, 2020
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.
December 16, 2020
You can now build and deploy source code to Cloud Run using a single command: gcloud beta run deploy --source .
December 14, 2020
Cloud Run container instances can now process up to 250 concurrent requests, see Configuring maximum concurrency. The default is still 80.
October 23, 2020
Cloud Run services can now be triggered using Eventarc (available in public preview)
October 19, 2020
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.
October 15, 2020
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.
October 13, 2020
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.
October 12, 2020
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
October 11, 2020
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.
October 06, 2020
Cloud Run now supports request timeouts up to 60 minutes. However, timeouts greater than 15 minutes are a beta feature.
March 30, 2020
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.
March 23, 2020
You can now restrict which regions are available to deploy Cloud Run (fully managed) services using an organization policy with a resource locations constraint.
March 16, 2020
Cloud Run (fully managed) now supports deploying container images from Cloud Artifact Registry
February 12, 2020
Cloud Run (fully managed) now supports rollbacks, gradual rollouts (blue/green deployments), and other traffic migration manipulations between revisions.
January 30, 2020
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)
January 27, 2020
The Cloud Run v1alpha1 API is deprecated and will be turned down. It is replaced by the Cloud Run v1 API
January 24, 2020
You can now allocate 2 vCPUs to Cloud Run (fully managed) services.
January 07, 2020
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.
Use custom revision names with the --revision-suffix command line flag.
Specify custom command and arguments for your deployed containers.
December 23, 2019
Cloud Run (fully managed) Service Level Agreement (SLA) has been updated to a Monthly Uptime Percentage of at least 99.95%
November 14, 2019
Cloud Run (fully managed) is now Generally Available (GA).
October 25, 2019
Legacy versions of the container instance metadata server have been removed.
October 22, 2019
Cloud Run (fully managed) free tier is now applied as a spending based discount.
October 21, 2019
Cloud Run is now covered by HIPAA Compliance.
October 01, 2019
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.