Deployment Strategies

DevOps, CI/CD & ToolingTopic 6 of 155 questions

Q1Kubernetes `RollingUpdate` vs `Recreate` deployment strategies: trade-offs and when to choose each

RollingUpdate keeps the lights on by overlapping two versions; Recreate turns the lights off so only one version ever runs.

Read Answer

Q2Comparing deployment strategies and their trade-offs: Recreate, Rolling, Blue-Green, Canary, A/B, Shadow

Pick the strategy by how much you are willing to spend to shrink risk and rollback time: zero downtime is the destination, these strategies are different roads to it.

Read Answer

Q3Rolling Updates, Fast Rollback, and Why Rollback May Not Fully Restore State

Rolling updates swap Pods gradually with maxSurge/maxUnavailable, rollout undo reverts the Pod template fast, but it never undoes ConfigMaps, Secrets, or database migrations.

Read Answer

Q4Blue-Green vs Canary vs Rolling deployment, and when to use each

Blue-Green switches all traffic at once between two full environments for instant cutover and rollback; Canary shifts a small, growing percentage to limit blast radius; Rolling replaces instances a few at a time with no extra environment.

Read Answer

Q5Deployment Strategies: Rolling Update, Blue-Green, and Canary

Rolling swaps instances gradually, blue-green flips all traffic between two full environments instantly, and canary shifts a small percentage first and ramps only if metrics stay healthy.

Read Answer