📄️ Deploy an Application
Deploy a container to Cloud Run, Kubernetes or Compute Engine. Use an Application when the platform builds the image. Use an ExternalApplication when the image already exists in a registry.
📄️ Provision a Database
Create a managed AlloyDB (PostgreSQL) database and give an application access to it. The platform sets up the network, firewall rules and encryption. It turns on automated backups for each new cluster. Google sets the schedule and the retention.
📄️ Create a Bucket
Create a private Cloud Storage bucket and give an application access to it. Buckets are private, encrypted at rest and versioned.
📄️ Manage Secrets
Declare a secret in a manifest, add its value in Google Cloud Secret Manager and inject it into an application. Never put a secret value in Git.
📄️ Migrate to Cloud Run
Move a service from Kubernetes or Compute Engine to Cloud Run. Cloud Run scales a service to zero when it has no traffic. The image does not change. See Architectural Overview for the reason this works.
📄️ Set Up a Custom Domain
Serve an application on a domain that you own, for example api.yourcompany.com. A PublicIngress creates the load balancer and the domain. An HttpRoute sends traffic to your application.
📄️ View Logs and Dashboards
The platform sets up logs, metrics, dashboards and a baseline set of alerts. You install no agents. Use the Google Cloud console of the project for your environment.
📄️ Manage Access
Give people access to a project through groups. An OrganizationUserGroup manifest defines a group. The permissions block of a project lists groups. Each change is a pull request, so Git records who asked, and who approved it when a rule requires approval.
🗃️ 9. Disaster Recovery
2 items
📄️ Set Up a Pub/Sub Topic
Create a Pub/Sub topic and let applications publish to it or subscribe to it. The platform encrypts topics at rest with Google-managed keys.
📄️ Provision a Redis Cache
Create a managed Redis instance (Memorystore) for a cache or for sessions. The instance is in the Shared VPC of the project. Only the private network can reach it.
📄️ Set Up a Repository and CI
Create a managed GitHub repository with generated CI, branch protection and a container image in Artifact Registry. Two manifests do this work: a GithubRepository and a BuildDefinition. See CI/CD for what the engine generates.
📄️ Run Database Migrations
Run a migration before each deployment of an application. Add a BEFORE job to the application and describe it in a JobConfig. The platform creates a Cloud Run Job. The main service deploys only after the job succeeds.
📄️ Deploy a Virtual Machine
Create a managed virtual machine, or a stateful cluster of machines. Use a VM for a workload that needs persistent disks, stable network identities or a custom operating-system image. Two manifests work together:
📄️ Set Up Private Ingress
Create an internal-only load balancer for services in different projects. A PrivateIngress keeps traffic in the private network of your organization. A PublicIngress exposes services to the internet.
📄️ Configure Egress Rules
Let the applications of a project call specific outside services. The platform denies outbound traffic from a project by default. Google's services, the Debian and Windows update servers and private addresses inside your network (10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16) are always allowed.
📄️ Adopt a Repository, DNS and Sign-in
Bring a repository, a domain and a sign-in flow that you already have under management. For a new repository, read Set Up a Repository and CI.
📄️ Control Costs
Two actions cut cost.
📄️ Manage MCP
Use manifests to control who can use the Model Context Protocol (MCP) with your organization. Use manifests also to run MCP servers of your own. Each change is a pull request, so Git records who asked for it.
📄️ Practical Guides
Each guide does one task. It lists the prerequisites, the steps, a minimal manifest and how to verify the result. The Manifest Reference lists every field. Samples & Templates has manifest sets that you can copy. Use Cases lists the tasks by goal.