Cloud Deploy

As explained in Google Anthos in Action

Cloud Deploy is a Google Cloud service that automates the promotion and deployment of application releases across defined target environments.

Cloud Deploy is a fully managed continuous-delivery service that promotes application releases through a defined sequence of target environments. Delivery pipelines control the sequence, while releases and rollouts manage application lifecycle and deployment progress. section 12.5 section 12.5.2

A typical Anthos CI/CD flow combines CI tooling, Cloud Build, Skaffold, Cloud Storage, Operations Suite, Pub/Sub, and GKE or Anthos clusters. Cloud Build uses Skaffold to render manifests and deploy them to the selected runtime. section 12.5.1

Configure a pipeline by:

• Defining a delivery pipeline with ordered targets such as test, staging, and production. section 12.5.2
• Defining target files that identify each GKE or Anthos cluster. section 12.5.2
• Providing a Skaffold configuration, container image, and Kubernetes manifest generated or prepared by CI. section 12.5.2
• Registering the resources, creating a release, and promoting or approving rollouts as required. section 12.5.2

Three-stage promotion pipeline

A delivery-pipeline.yaml file can define web-app with serial stages targeting test, staging, and prod. Register the pipeline and target files with gcloud deploy apply, then create a release with gcloud deploy releases create RELEASE_NAME --delivery-pipeline=PIPELINE_NAME. Promote it with gcloud deploy releases promote or require approval on a production target.

Figure 12.36 The Cloud Deploy CI/CD ecosystem

The ecosystem diagram maps Cloud Deploy to CI tooling, Cloud Build, Skaffold, observability, messaging, storage, and target clusters. section 12.5.1

How Google Anthos in Action covers it

How deep it goes

Explains architecture, manifests, targets, Skaffold configuration, registration commands, releases, promotions, and manual approvals.

Examples

Uses test-staging-production pipelines, separate target YAML files, Skaffold configuration, gcloud commands, and approval settings.

What it assumes

Assumes three GKE or Anthos clusters, a container image, and Kubernetes manifests available from CI.

What you can do after

Operate releases by registering pipelines, creating releases, promoting rollouts, and approving or rejecting target deployments.

How it connects

Connects continuous integration, Cloud Build, Skaffold, Kubernetes manifests, Cloud Storage, Pub/Sub, Operations Suite, GKE, and Anthos.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Related concepts

• trajectoryproduces · A trajectory is an ordered sequence of states, actions, events, or operations that records or describes progression through successive steps or over time.
• deployment pipelineuses · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
• continuous deploymentimplements · Continuous deployment is a software delivery practice in which validated changes are automatically released to a target environment, typically production, without manual approval.
• Cloud Builduses · Cloud Build is a managed Google Cloud service that executes automated build, test, and deployment steps from source code or configuration changes.
• Kubernetes Engineuses · Google Kubernetes Engine is Google Cloud’s managed service for running Kubernetes clusters and containerized workloads.
• releaseuses · A software release is a version or set of changes made available to intended recipients for deployment or use.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.