---
cuppy_hub: gcp
cuppy_path: reference/iac/deployment-manager-status.md
cuppy_section: docs
cuppy_doc: XD6V-NSWD
cuppy_doc_uuid: 80b705e7-ef5c-40ea-99c0-f348aabcf653
cuppy_permalink: https://cuppy.io/gcp/d/XD6V-NSWD
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/gcp/docs/reference/iac/deployment-manager-status
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: ac81d0f5f1fdf94860e6d9fccce14b9dec68a62d60a543693857cd6d18cb780a
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---


# 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

1. **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.
2. **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.
3. **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`).


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 91 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/gcp/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->