Cloud Deploy release notes

The Cloud Deploy image now uses a Google-specific fork of Skaffold. The Skaffold version that you see if you run gcloud deploy releases describe, or if you view the release in the Google Cloud Console, is now cd-skaffold instead of a version number.

The Cloud Deploy image now uses Kubectl Kustomize.

By default, Cloud Deploy now uses the Kustomize built into kubectl. Previously, the default version of Kustomize was the version embedded in the Cloud Deploy image. Now it's the version used by kubectl.

You can still use kustomize directly (not through kubectl) by specifying the kustomize version when you create a release.

Support for deploying Cloud Run worker pools is now generally available (GA).

You can now analyze the performance of your deployed applications using the monitoring platform of your choice and automatically trigger actions such as rollbacks. This feature is generally available.

You can now provide user-defined actions using tasks. This includes deploy hooks, deployment verification, analysis, and custom target types. This feature is generally available.

Cloud Deploy is now available in the following region: asia-southeast3 (Bangkok)

You can now deploy containerized workloads to Cloud Run worker pools (in Preview).

The limit on deployment minutes per delivery pipeline has been removed. The only quota now enforced in Cloud Deploy is the system limit of 18,000 API requests per minute per region. Learn more.

We now upgrade the tools used for deployments more frequently. This includes tools like Skaffold, Kubectl, and Helm. You can also select specific versions of these tools when you create a release.

You can now use custom constraints with Organization Policy to provide more granular control over specific fields for some Cloud Deploy resources. For more information, see Use custom organization policies.

Cloud Deploy now uses Skaffold 2.16 as the default Skaffold version, as of May 23, 2025, for all target types.

Cloud Deploy support for timed promote is now generally available.

Cloud Deploy support for deploy policies is now generally available.

Cloud Deploy support for repair rollout automation is now generally available.

Cloud Deploy is now available in the following regions:

• northamerica-south1 (Mexico)
• europe-north2 (Stockholm)

Cloud Deploy now uses Skaffold 2.14 as the default Skaffold version, as of March 21, 2025, for all target types.

You can now connect to your GKE cluster's DNS-based endpoint, simplifying networking configuration when talking to private clusters from Cloud Deploy. Learn more.

You can now automatically promote releases across targets at scheduled times, in preview.

You can now automatically retry failed rollouts, and automatically roll back to the most recent successful rollout, in preview.

You can now block rollouts during a specified time window, using deploy policies, in preview.

Cloud Deploy now uses Skaffold 2.13 as the default Skaffold version, as of October 4, 2024, for all target types.

Cloud Deploy is now available in the following region: africa-south1 (Johannesburg)

You can now set the logging level to debug, or the equivalent, for Skaffold, gcloud, and kubectl, using the verbose flag in each target's execution environment.

Cloud Deploy now supports deploying using a proxy for Google Kubernetes Engine targets. Learn more.

Cloud Deploy now uses Skaffold 2.11 as the default Skaffold version for all target types.

Cloud Deploy support for deploy automation is now generally available.

Cloud Deploy support for custom targets is now generally available.

Cloud Deploy now uses Skaffold 2.10 as the default Skaffold version for all target types.

Google Cloud Deploy is now available in the following regions:

• me-central1 (Doha)
• me-central2 (Dammam)
• europe-west12 (Turin)
• europe-west10 (Berlin)

You can now define custom target types and deploy to targets of those types, in preview.

You can now access