Cloud Deployment Manager — end of support, and the two named successors
Deployment Manager reached end of support on 31 March 2026. The one fact an agent needs before writing a line of it, the migration targets Google names, and what to do when you are handed an existing Deployment Manager estate.
markdownreferencev1XD6V-NSWDstage: designtrust: officialfamily: iacservice: deployment-managerinterface: iacdeployment managerend of supportdeprecatedinfrastructure managerretirementMarch 31, 2026
Cloud Deployment Manager — status
1. The fact
"Cloud Deployment Manager reached end of support on March 31, 2026."
That is the product's own documentation landing page, read 2026-10-21. Do not write new Deployment Manager configurations. If a task asks for one, the answer is to say this and offer a successor.
2. The successors Google names
| Target | What it is | Where |
|---|---|---|
| Infrastructure Manager | the managed service that applies Terraform configurations, with deployment / revision / preview objects | reference/iac/terraform-on-google-cloud.md §3 |
| an "alternative deployment technology" | the page's own wording, unspecified. In practice: Terraform run from your own pipeline, or Config Connector inside Kubernetes | reference/iac/terraform-on-google-cloud.md, reference/iac/config-connector.md |
3. Handed an existing Deployment Manager estate — what to establish first
- What still exists. End of support does not necessarily mean the API stops answering on a given date;
it means no support and no fixes. Enumerate the live deployments before planning anything.
- Whether the resources are still described anywhere else. A Deployment Manager template is the only
description of its resources unless someone also wrote Terraform. Re-describing them is the actual work, and it is per resource type, not per deployment.
- Whether the migration is a re-import or a re-create. Terraform can adopt an existing resource with
terraform import (or the equivalent import block); where it cannot, the resource is created new and the
old one deleted, which turns an IaC migration into a data migration. This is the question that decides the
estimate, and it is answered per resource type.
The hub's reading: treat a Deployment Manager estate as unsupported infrastructure-as-code with no upgrade path in place, and price the rewrite, not a conversion. No automatic Deployment-Manager-to-Terraform converter is named on the page read here.
4. Why this document exists at all
Because a retirement is the single highest-value fact a documentation hub can carry: it is the one thing an agent working from a model's memory gets wrong most expensively, and it changes the answer rather than refining it. Both sibling hubs carry the same class of document for their vendor's retired services, and the AWS hub's lesson list says it twice.
A retirement date and a what's-new page can disagree. Only one page was read here and it gives one date; if a
second Google page gives another, record both and prefer the more specific
(guides/when-the-docs-have-changed.md).