Question

Your team uses Cloud Deploy to promote a containerized application through dev, staging, and prod GKE clusters. Each environment requires different Kubernetes manifest values (replica counts, resource limits, and namespace). You want a single delivery pipeline that renders environment-specific manifests at release creation time without maintaining separate pipeline definitions per target. What is the recommended approach?

Accepted Answer

Define a single Skaffold configuration with profiles per target and reference them in the Cloud Deploy pipeline stages so manifests are rendered per-target during release creation.

Answer

Create three separate Cloud Deploy delivery pipelines, one per environment, each pointing to its own hardcoded manifest set.

Answer

Manually run kubectl apply with edited manifests for each cluster after Cloud Deploy promotes the artifact.

Answer

Store fully rendered manifests for all environments in the container image and select them at runtime with an entrypoint script.