Question

A development team currently uses hand-written shell scripts invoked from a Cloud Build step to promote container images through dev, staging, and production GKE clusters. Promotions are error-prone, lack a consistent approval step, and offer no easy way to roll back to a previously deployed release. As the architect, you must advise the team on a Google Cloud managed service that provides a declarative delivery pipeline with defined promotion sequences between targets, approval gates, and one-command rollback, while minimizing custom scripting. What do you recommend?

Accepted Answer

Adopt Cloud Deploy, defining a delivery pipeline with ordered targets for dev, staging, and production, using its built-in promotion, approvals, and rollback.

Answer

Continue with Cloud Build but move the shell scripts into a reusable custom builder image stored in Artifact Registry.

Answer

Use Config Sync to reconcile each cluster against a Git repository, relying on directory structure to represent each environment.

Answer

Deploy directly with kubectl apply from a Cloud Scheduler job that runs on a fixed nightly cadence for each cluster.