Course contentsShow
← Cloud and Infrastructure
Lesson 936 of 2,98918. Google Cloud Deployment ManagerFree lesson

Deployment Manager Architecture and Components

Learn the core components: configurations, templates, manifests, and how Deployment Manager interacts with GCP APIs.

Deployment Manager Architecture and Components

Important Notice: Google Cloud Deployment Manager reached end of support on March 31, 2026. Direct all new infrastructure work to Google Cloud Infrastructure Manager or Terraform. The following content is provided strictly as legacy reference for understanding and maintaining existing deployments. Do not use gcloud deployment-manager commands to spin up new infrastructure; treat them entirely as legacy reference commands for maintaining existing, older deployments.

What you'll learn: How Google Cloud Deployment Manager's core components worked together to automate infrastructure provisioning in legacy systems.

The Big Picture

Google Cloud Deployment Manager operated like a construction company with blueprints, foremen, and inspection logs. It took declarative descriptions of your infrastructure and turned them into real GCP resources by coordinating with Google Cloud APIs.

Core Components

Configurations are YAML or Python files that declared what you wanted to build—the complete specification of your infrastructure. Think of these as your master blueprint listing every resource needed for a deployment.

Templates are reusable building blocks within configurations. They allowed engineers to define patterns once and reference them multiple times. Instead of repeatedly describing identical virtual machine setups, you could create a template and reuse it across your deployment.

Manifests are read-only snapshots created after each deployment. Deployment Manager generated these automatically to show the exact state of resources at a given point in time—like a timestamped photo of your infrastructure.

Resources are the actual GCP components (VMs, networks, databases) that Deployment Manager created by calling Google Cloud APIs on your behalf.

How It Worked Together

When a configuration was submitted, Deployment Manager parsed the templates, expanded them into a complete resource list, and then made the appropriate API calls to GCP services. Each successful deployment generated a manifest documenting exactly what was created. This architecture separated intent (configurations/templates) from execution (API calls) from record-keeping (manifests).

The system was declarative—engineers described the end state, and Deployment Manager figured out the API sequence needed to achieve it. Understanding this architecture remains highly valuable for interpreting manifests and configuration files when migrating legacy environments to modern infrastructure-as-code tools.

Key Takeaway: As a legacy tool, Deployment Manager used configurations and templates to define infrastructure, called GCP APIs to create resources, and stored manifests as deployment records. Remember to use Google Cloud Infrastructure Manager or Terraform for all new infrastructure deployments.