Stay organized with collections
Save and categorize content based on your preferences.
Cloud Deploy is a managed service that automates delivery of your
applications to a series of target
environments in a defined promotion sequence. When you want to deploy your
updated application, you create a release,
whose lifecycle
is managed by a delivery pipeline.
How a Cloud Deploy pipeline works
The Cloud Deploy delivery pipeline contains the following information:
A name, which you use when referring to the delivery pipeline, and a
description.
The promotion sequence, describing the order in which to deploy to the
configured targets.
Also optionally, the target definitions themselves.
Targets can be defined in the
same delivery pipeline configuration file, or in
one or more separate files. Multiple delivery pipelines can use the same
target or targets, but a given target can be used only once in a given delivery
pipeline.
The Cloud Deploy delivery process
The following is a description of what happens in a simple Cloud Deploy
continuous delivery scenario.
This configuration file defines the promotion sequence in which to deploy
your application to a series of targets.
You also need a configuration
for Skaffold, which Cloud Deploy needs in order to
perform render and deploy operations.
You define your targets, either in the pipeline configuration file or in a
separate file or files.
You register your pipeline with the Cloud Deploy service.
Now that the service knows about your application, it manages the deployment
to targets according to your defined promotion sequence.
The output of your CI process includes a call to Cloud Deploy to
initiate your delivery pipeline.
This call creates a release resource, representing the rendered manifest
for each target, each of which is generated using the provided rendering
source, skaffold.yaml, and references to specific container images to deploy.
For this first call to create a release,
Cloud Deploy automatically creates a rollout
resource, which associates the release with the first target environment.
Based on that rollout, your application is deployed to the first target.
You can use any CI tool as long as it outputs one or more container images to
provide to your Cloud Deploy delivery pipeline.
Furthermore, the call to create a release and invoke a delivery pipeline
doesn't have to come from the CI tool. It can come from a script or any
system responding to the completion of the CI process.
When you're ready to deploy your application to the next target, you call
Cloud Deploy to promote it.
In each case, the call to invoke the promotion causes Cloud Deploy
to create a new rollout.
Promotion continues through all targets in your promotion sequence, the last
of which is prod (or whatever name you use for your final target to put the
application into production).
Throughout pipeline execution, Cloud Deploy collects metrics and
audit details.
Promotion
To promote a release
is to deploy it to the next target in the promotion sequence defined in your
pipeline. The first call to Cloud Deploy creates a release, then a
rollout resource that's used to deploy to the first target in the promotion
sequence. Each subsequent call to promote the release results in a rollout to
the next target.
Approvals
You can specify that an approval is needed for promotion to any target. For
example, you might want to require approval for promotion into a production
target. To require approval for a target, set the requireApproval property in
the target definition.
When a target requires approval, Cloud Deploy generates a
Pub/Sub message that can be consumed by an integrated system.
For example, a ticketing system could subscribe to the message to kick off an
approval workflow.
See Require approval for more
information on promotions and managing approval for promotions.
Notifications
Cloud Deploy provides Pub/Sub notifications for the following
events:
Render: start, success, and failure
Deploy: start, success, and failure
Approval required
Approval approved
Approval rejected
Cloud Deploy uses a Pub/Sub topic to send these
notifications.
Cloud Deploy supports rolling back your deployed application in any
target. A rollback in Cloud Deploy consists of triggering a rollout
against the last successfully deployed release. The new rollout uses the same
parameters that were used in that successful deployment.
Cloud Deploy uses Skaffold for rendering, deployment,
and verification. With Skaffold, you can also easily connect your local
development loop to a Cloud Deploy continuous delivery pipeline.
To learn more about how Cloud Deploy integrates with Skaffold, see
the Skaffold overview.
Cloud Deploy with other Google Cloud tools
Cloud Deploy supports almost any tool upstream in a CI/CD pipeline.
That is, you can use any development environment and source code repository, any
continuous integration (CI) system, and any artifact repository.
Downstream, Cloud Deploy deploys to Google Kubernetes Engine,
Cloud Run, and GKE Enterprise.
If you used mostly Google Cloud tools, your source-to-prod flow
would look like this:
Cloud Code extends several popular IDEs (VS Code, IntelliJ,
Cloud Shell) to make it easier to build applications to deploy and run on
Google Cloud.
Use Skaffold to manage your local development loop.
Cloud Deploy uses Skaffold, through Cloud Build, to
render and deploy your manifests. This integration means that you need to
maintain a skaffold.yaml file, but does not otherwise mean you need to make
Skaffold part of your local development flow. But you can take advantage of
it for continuous development.
Build your application using Cloud Build.
Cloud Build lets you set up a CI pipeline that can be
triggered from a commit to your source code repository. The output from
Cloud Build will be artifacts including deployable container
images. You can add a call to Cloud Deploy to create a release
and invoke your delivery pipeline.
Store your artifacts in Artifact Registry.
Cloud Deploy retrieves the container image or images from
Artifact Registry, which lets you centrally store
artifacts and dependencies.
Configure your delivery pipeline in Cloud Deploy to take the
container image and deploy it in a progression of n targets.
Each of those targets identified in your delivery pipeline represents a
GKE cluster, Cloud Run, or
GKE cluster where your application is ultimately deployed.
Manage your application on GKE, Cloud Run
or GKE Enterprise.
GKE is the
Google Cloud managed environment for running containerized
applications on Kubernetes.
With Cloud Run, you can run containers in a
serverless environment.
GKE Enterprise provides a consistent development
and operations experience for cloud and on-premises environments.
Monitor the performance of your application using Google Cloud Observability.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eCloud Deploy automates application delivery to multiple target environments through a defined promotion sequence managed by a delivery pipeline.\u003c/p\u003e\n"],["\u003cp\u003eA Cloud Deploy pipeline includes a name, promotion sequence, and optional labels, annotations, and target definitions, with targets being configurable within the pipeline or in separate files.\u003c/p\u003e\n"],["\u003cp\u003eThe delivery process involves defining the pipeline and targets, registering the pipeline, initiating the pipeline via a CI tool, and promoting the application through subsequent targets, each generating a new rollout.\u003c/p\u003e\n"],["\u003cp\u003eCloud Deploy supports approvals for promotion to any target, which triggers a notification process that integrated systems can use to manage the approval workflow.\u003c/p\u003e\n"],["\u003cp\u003eCloud Deploy uses Skaffold for rendering, deployment, and verification, integrates with various CI/CD tools, and works with Google Cloud services like GKE, Cloud Run, GKE Enterprise, Cloud Build, and Artifact Registry.\u003c/p\u003e\n"]]],[],null,["# Overview of Cloud Deploy\n\nCloud Deploy is a managed service that automates delivery of your\napplications to a series of [target](/deploy/docs/terminology#target)\nenvironments in a defined promotion sequence. When you want to deploy your\nupdated application, you create a [release](/deploy/docs/terminology#release),\nwhose [lifecycle](/deploy/docs/architecture#how_they_fit_together_to_deliver_your_release)\nis managed by a [delivery pipeline](/deploy/docs/terminology#delivery_pipeline).\n\nHow a Cloud Deploy pipeline works\n---------------------------------\n\nThe Cloud Deploy delivery pipeline contains the following information:\n\n- A name, which you use when referring to the delivery pipeline, and a\n description.\n\n- The promotion sequence, describing the order in which to deploy to the\n configured [targets](/deploy/docs/terminology#target).\n\n- Optionally, [labels and annotations](/deploy/docs/labels-annotations).\n\n- Also optionally, the target definitions themselves.\n\nTargets can be [defined](/deploy/docs/config-files#target_definitions) in the\nsame delivery pipeline [configuration file](/deploy/docs/config-files), or in\none or more separate files. Multiple delivery pipelines can use the same\ntarget or targets, but a given target can be used only once in a given delivery\npipeline.\n\n### The Cloud Deploy delivery process\n\nThe following is a description of what happens in a simple Cloud Deploy\ncontinuous delivery scenario.\n\n1. You define your [delivery pipeline](/deploy/docs/terminology#delivery_pipeline)\n in a [YAML configuration file](/deploy/docs/config-files#structure_of_a_delivery_pipeline_configuration_file).\n\n This configuration file defines the promotion sequence in which to deploy\n your application to a series of [targets](/deploy/docs/terminology#target).\n\n You also need a [configuration](https://skaffold.dev/docs/references/yaml/)\n for [Skaffold](/skaffold), which Cloud Deploy needs in order to\n perform render and deploy operations.\n2. You define your targets, either in the pipeline configuration file or in a\n separate file or files.\n\n3. You register your pipeline with the Cloud Deploy service.\n\n Now that the service knows about your application, it manages the deployment\n to targets according to your defined promotion sequence.\n4. The output of your CI process includes a call to Cloud Deploy to\n initiate your delivery pipeline.\n\n This call creates a `release` resource, representing the rendered manifest\n for each target, each of which is generated using the provided rendering\n source, skaffold.yaml, and references to specific container images to deploy.\n For this first call to create a [release](/deploy/docs/terminology#release),\n Cloud Deploy automatically creates a [`rollout`](/deploy/docs/terminology#rollout)\n resource, which associates the release with the first target environment.\n Based on that rollout, your application is deployed to the first target.\n\n You can use any CI tool as long as it outputs one or more container images to\n provide to your Cloud Deploy delivery pipeline.\n\n Furthermore, the call to create a release and invoke a delivery pipeline\n doesn't have to come from the CI tool. It can come from a script or any\n system responding to the completion of the CI process.\n5. When you're ready to deploy your application to the next target, you call\n Cloud Deploy to promote it.\n\n In each case, the call to invoke the promotion causes Cloud Deploy\n to create a new rollout.\n6. Promotion continues through all targets in your promotion sequence, the last\n of which is `prod` (or whatever name you use for your final target to put the\n application into production).\n\n The process of release creation and promotion is described in more detail in\n [Cloud Deploy service architecture](/deploy/docs/architecture#how_they_fit_together_to_deliver_your_release).\n\nThroughout pipeline execution, Cloud Deploy collects metrics and\n[audit](/deploy/docs/audit-logs) details.\n\n### Promotion\n\nTo [promote a release](/deploy/docs/promote-release)\nis to deploy it to the next target in the promotion sequence defined in your\npipeline. The first call to Cloud Deploy creates a `release`, then a\n`rollout` resource that's used to deploy to the first target in the promotion\nsequence. Each subsequent call to promote the release results in a rollout to\nthe next target.\n\n### Approvals\n\nYou can specify that an approval is needed for promotion to any target. For\nexample, you might want to require approval for promotion into a production\ntarget. To require approval for a target, set the `requireApproval` property in\nthe [target definition](/deploy/docs/config-files#target_definitions).\n\nWhen a target requires approval, Cloud Deploy generates a\nPub/Sub message that can be consumed by an integrated system.\nFor example, a ticketing system could subscribe to the message to kick off an\napproval workflow.\n\nSee [Require approval](/deploy/docs/promote-release#require_approval) for more\ninformation on promotions and managing approval for promotions.\n\n### Notifications\n\nCloud Deploy provides Pub/Sub notifications for the following\nevents:\n\n- Render: start, success, and failure\n- Deploy: start, success, and failure\n- Approval required\n- Approval approved\n- Approval rejected\n\nCloud Deploy uses a Pub/Sub topic to send these\nnotifications.\n\nSee [Using Cloud Deploy notifications](/deploy/docs/subscribe-deploy-notifications) for more details.\n\n### Rollbacks\n\nCloud Deploy supports rolling back your deployed application in any\ntarget. A rollback in Cloud Deploy consists of triggering a rollout\nagainst the last successfully deployed release. The new rollout uses the same\nparameters that were used in that successful deployment.\n\nSee [Rolling back a deployment](/deploy/docs/roll-back) for more details.\n\nAbout Skaffold and Cloud Deploy\n-------------------------------\n\nCloud Deploy uses [Skaffold](/skaffold) for rendering, deployment,\nand verification. With Skaffold, you can also easily connect your local\ndevelopment loop to a Cloud Deploy continuous delivery pipeline.\n\nTo learn more about how Cloud Deploy integrates with Skaffold, see\nthe [Skaffold overview](/deploy/docs/using-skaffold).\n\nCloud Deploy with other Google Cloud tools\n------------------------------------------\n\nCloud Deploy supports almost any tool upstream in a CI/CD pipeline.\nThat is, you can use any development environment and source code repository, any\ncontinuous integration (CI) system, and any artifact repository.\n\nDownstream, Cloud Deploy deploys to Google Kubernetes Engine,\nCloud Run, and GKE Enterprise.\n\nIf you used mostly Google Cloud tools, your source-to-prod flow\nwould look like this:\n\n1. Use [Cloud Code](/code/docs) to create your application source.\n\n Cloud Code extends several popular IDEs (VS Code, IntelliJ,\n Cloud Shell) to make it easier to build applications to deploy and run on\n Google Cloud.\n2. Use [Skaffold](https://skaffold.dev) to manage your local development loop.\n\n Cloud Deploy uses Skaffold, through Cloud Build, to\n render and deploy your manifests. This integration means that you need to\n maintain a `skaffold.yaml` file, but does not otherwise mean you need to make\n Skaffold part of your local development flow. But you can take advantage of\n it for [continuous development](https://skaffold.dev/docs/workflows/dev/).\n3. Build your application using Cloud Build.\n\n [Cloud Build](/build/docs) lets you set up a CI pipeline that can be\n triggered from a commit to your source code repository. The output from\n Cloud Build will be artifacts including deployable container\n images. You can add a call to Cloud Deploy to create a release\n and invoke your delivery pipeline.\n4. Store your artifacts in Artifact Registry.\n\n Cloud Deploy retrieves the container image or images from\n [Artifact Registry](/artifact-registry/docs), which lets you centrally store\n artifacts and dependencies.\n5. Configure your delivery pipeline in Cloud Deploy to take the\n container image and deploy it in a progression of *n* targets.\n\n Each of those targets identified in your delivery pipeline represents a\n GKE cluster, Cloud Run, or\n GKE cluster where your application is ultimately deployed.\n6. Manage your application on GKE, Cloud Run\n or GKE Enterprise.\n\n [GKE](/kubernetes-engine/docs) is the\n Google Cloud managed environment for running containerized\n applications on Kubernetes.\n\n With [Cloud Run](/run/docs), you can run containers in a\n serverless environment.\n\n [GKE Enterprise](/anthos/docs) provides a consistent development\n and operations experience for cloud and on-premises environments.\n7. Monitor the performance of your application using Google Cloud Observability.\n\n [Google Cloud Observability](/stackdriver/docs) offers integrated monitoring and\n logging for your application.\n\nWhat's next\n-----------\n\n- For a quick-and-easy look at how to create a delivery pipeline and use it to\n deploy an application, try the [quickstarts](/deploy/docs/quickstarts).\n\n- Try out one of the [Cloud Deploy walkthroughs](/deploy/docs/tutorials).\n\n- Learn more about [how Cloud Deploy components work together](/deploy/docs/architecture).\n\n- Review [Google Cloud Well-Architected Framework: Operational excellence](/architecture/framework/operational-excellence)\n for articles on how to use the principles of operational excellence to build an\n automated delivery foundation.\n\n- [Learn how to combine Google Cloud CI/CD tools to develop and deliver\n software effectively to GKE](https://cloud.google.com/architecture/app-development-and-delivery-with-cloud-code-gcb-cd-and-gke)."]]