Stay organized with collections
Save and categorize content based on your preferences.
Cloud Deploy supports deployment strategies. A deployment strategy is any of
several techniques for deploying changes to your application while minimizing
impact to users.
What deployment strategies does Cloud Deploy support?
Cloud Deploy supports the following deployment strategies:
The standard deployment strategy simply deploys an application to a target
runtime or runtimes. The deployment is not performed progressively, and there
is no splitting between the old and new versions of your application.
With a standard deployment, you can easily roll back your release, you can
verify your deployment, and you can deploy to more than one target at the same
time.
A canary deployment is a progressive deployment of your application, such
that your app is deployed at first to a portion of your infrastructure and can
be tested there before being rolled out further. A canary deployment reduces
the risk of introducing changes by reducing the number of users likely to be
affected by a bug.
For example, with a 50% canary deployment to Cloud Run, half the
traffic would be directed to the new revision, with half of it still directed
to the old revision. After testing to help ensure stability, you would advance
the rollout to 100%. With Cloud Deploy, you can specify any
progression of percentages (except partial percentages, like 20.5%).
Both of these deployment strategies support all of the runtime environments that
Cloud Deploy supports. Also, all deployment strategies support
rolling back,
canceling rollouts,
and deploying to more than one target at the same time
(parallel deployment).
Why phases are sometimes skipped
Because a canary runs against an existing version of an application
(progressively replacing that version), the canary strategy can't be performed
if there's no version deployed yet that Cloud Deploy can recognize.
This means that if you deploy an application for the first time to a given
target, and you use a canary deployment strategy, the rollout might skip the
canary phase or phases. In this case, after Cloud Deploy skips to
the stable phase, and you click Advance Rollout to initiate the stable
phase, the application gets deployed fully to that target, and you can
now run a canary against it with your next set of changes. Clicking Advance
Rollout constitutes an acknowledgement that we've skipped the canary phases
that were not applicable for this deployment.
Use parallel deployment with a deployment strategy
[[["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 offers two main deployment strategies: standard deployment, which deploys an application without progressive rollout, and canary deployment, which progressively rolls out the application to reduce risk.\u003c/p\u003e\n"],["\u003cp\u003eStandard deployment allows for easy rollbacks, deployment verification, and simultaneous deployment to multiple targets, but does not perform deployments progressively.\u003c/p\u003e\n"],["\u003cp\u003eCanary deployments reduce the risk of introducing changes by initially deploying to a subset of the infrastructure for testing before a full rollout.\u003c/p\u003e\n"],["\u003cp\u003eCloud Deploy's canary strategy may skip phases if no prior version of the application is deployed, which then proceeds directly to the stable phase.\u003c/p\u003e\n"],["\u003cp\u003eBoth standard and canary strategies support all runtime environments supported by Cloud Deploy and can be used with parallel deployment to multiple targets simultaneously.\u003c/p\u003e\n"]]],[],null,["# Use a deployment strategy\n\nCloud Deploy supports deployment strategies. A deployment strategy is any of\nseveral techniques for deploying changes to your application while minimizing\nimpact to users.\n\nWhat deployment strategies does Cloud Deploy support?\n-----------------------------------------------------\n\nCloud Deploy supports the following deployment strategies:\n\n- [Standard deployment](/deploy/docs/deploying-application)\n\n The standard deployment strategy simply deploys an application to a target\n runtime or runtimes. The deployment is not performed progressively, and there\n is no splitting between the old and new versions of your application.\n\n With a standard deployment, you can easily roll back your release, you can\n verify your deployment, and you can deploy to more than one target at the same\n time.\n- [Canary deployment](/deploy/docs/deployment-strategies/canary)\n\n A canary deployment is a progressive deployment of your application, such\n that your app is deployed at first to a portion of your infrastructure and can\n be tested there before being rolled out further. A canary deployment reduces\n the risk of introducing changes by reducing the number of users likely to be\n affected by a bug.\n\n For example, with a 50% canary deployment to Cloud Run, half the\n traffic would be directed to the new revision, with half of it still directed\n to the old revision. After testing to help ensure stability, you would advance\n the rollout to 100%. With Cloud Deploy, you can specify any\n progression of percentages (except partial percentages, like 20.5%).\n\nBoth of these deployment strategies support all of the runtime environments that\nCloud Deploy supports. Also, all deployment strategies support\n[rolling back](/deploy/docs/roll-back),\n[canceling rollouts](/deploy/docs/deployment-strategies/manage-rollout#cancel_rollout),\nand deploying to more than one target at the same time\n([parallel deployment](/deploy/docs/parallel)).\n\nWhy phases are sometimes skipped\n--------------------------------\n\nBecause a canary runs against an existing version of an application\n(progressively replacing that version), the canary strategy can't be performed\nif there's no version deployed yet that Cloud Deploy can recognize.\n\nThis means that if you deploy an application for the first time to a given\ntarget, and you use a canary deployment strategy, the rollout might skip the\ncanary phase or phases. In this case, after Cloud Deploy skips to\nthe stable phase, and you click **Advance Rollout** to initiate the `stable`\nphase, the application gets deployed fully to that target, and you can\nnow run a canary against it with your next set of changes. Clicking **Advance\nRollout** constitutes an acknowledgement that we've skipped the canary phases\nthat were not applicable for this deployment.\n\n### Use parallel deployment with a deployment strategy\n\nYou can use a deployment strategy and still\n[deploy to more than one target at the same time](/deploy/docs/parallel).\n\nSee [Using parallel deployment with a canary deployment strategy](/deploy/docs/deployment-strategies/canary#parallel_canary)\nto find out how to do this with canary.\n\nWhat's next\n-----------\n\n- Try the quickstart: [Canary deploy an application to a target](/deploy/docs/deploy-app-canary)\n\n- Learn how to use the [canary deployment strategy](/deploy/docs/deployment-strategies/canary)\n\n- Find out how to [manage the lifecycle of your canary's rollouts](/deploy/docs/deployment-strategies/manage-rollout)."]]
