Question

Your team is migrating from ad-hoc kubectl deployments to Google Cloud Deploy. You must define a repeatable path where every release flows through dev, then staging, then production GKE clusters. You want the sequence of environments and the manual promotion between them expressed as configuration-as-code that lives in your Git repository and is applied to Cloud Deploy. Which resource should you define to establish this ordered progression of environments?

Accepted Answer

A DeliveryPipeline resource with a serial pipeline listing the dev, staging, and production targets in order

Answer

Three separate Cloud Build triggers, one per environment, chained by pub/sub notifications

Answer

A single Target resource that references all three clusters using a multi-cluster selector

Answer

A Skaffold profile per environment referenced directly from a Cloud Build pipeline