What it does
Google Cloud Deploy is a managed continuous delivery service for moving an application release through target environments. It sits after a build: a team's CI process creates deployable artifacts, then Cloud Deploy creates a release, manages rollouts, and can promote that release to later targets. The official quickstart shows a prebuilt image progressing across Google Kubernetes Engine clusters.
Use Cloud Deploy after the build is ready
Google's deployment guide explicitly places Cloud Deploy after regular continuous integration: CI creates the deployable artifact, then the team initiates a delivery pipeline by creating a release. A release is associated with a pipeline and its targets; the pipeline manages the release's progression. This separation is useful when the existing CI system should continue compiling and testing code while a dedicated service controls deployment order.
The GKE quickstart creates a delivery pipeline and targets, points Skaffold configuration at a prebuilt container image, creates a release that rolls out to the first target, then promotes it to the next target and reviews rollout status. The documentation also lists Cloud Run as a runtime option. These are documented steps, not a deployment performed for this record. The chosen GKE path requires a Google Cloud project and target clusters, plus the pipeline and Skaffold configuration. The pricing URL opened during research returned only its page title, so the billing model and current rates remain unresolved.
Strengths
- The documented workflow separates artifact production by CI from release creation and deployment progression.
- A delivery pipeline can advance a release through targets, with rollout status available for review.
- Official guides cover deployment targets including GKE and Cloud Run.
Watch out for
- The GKE quickstart requires target clusters, a configured delivery pipeline, a Skaffold configuration, and a deployable image.
- Cloud Deploy handles release and deployment progression; the documented flow expects CI to create artifacts before release creation.
Best for
- Google Cloud teams that need controlled promotion of an already-built application release across environments.
- Teams deploying container applications to GKE or Cloud Run who want rollout progression separated from CI builds.
Sources
- Cloud Deploy - Fully Managed Continuous Delivery | Google Cloud (Oct 25, 2026)
- Deploy your application | Google Cloud Documentation (Oct 25, 2026)
- Quickstart: Deploy an app to GKE using Cloud Deploy | Google Cloud Documentation (Oct 25, 2026)
- Cloud Deploy pricing | Google Cloud (Oct 25, 2026)