Question

Your team runs a stateless HTTP API on GKE and uses Cloud Deploy to promote releases through dev, staging, and prod. During production rollouts, the SRE team requires that new pods gradually replace old pods while keeping the service continuously available, without provisioning a duplicate set of infrastructure or maintaining a separate parallel environment. They also want to minimize additional compute cost during the rollout. Which deployment strategy should you configure in the Cloud Deploy delivery pipeline for the production target?

Accepted Answer

A rolling update strategy that incrementally replaces old Pods with new Pods using the Kubernetes Deployment's maxSurge and maxUnavailable settings

Answer

A blue-green strategy that spins up a full second environment and switches traffic after verification

Answer

A canary strategy with 5%, 25%, and 100% phases routing a subset of traffic to the new version

Answer

A recreate strategy that terminates all existing Pods before starting the new version