KCNA ยท Application delivery and debugging
Deployment strategies
Rolling update, recreate, blue/green, canary, progressive delivery and rollback.
Key points
- Recreate: stops all old Pods, then starts new ones (brief downtime).
- Rolling update: replaces Pods gradually; old and new run side by side.
- Blue/green: two full environments, traffic switches at once, old kept for instant rollback.
- Canary: a small share of traffic goes to the new version first.
- Progressive delivery: automates widening by metrics, aborts on failure.
- kubectl rollout undo reverts a Deployment.
Practice questions
Which strategy replaces Pods gradually so old and new versions briefly run together?
- Recreate
- Rolling update
- Blue/green
- Shadow database
Show answer
Answer: B. Rolling update
Rolling update swaps Pods in batches. Recreate stops everything first, and blue/green switches whole environments.
Which statements describe blue/green deployment?
- Two complete environments exist, one live and one idle
- Traffic is switched from one environment to the other in one step
- Rollback can be as simple as switching traffic back
- Traffic is shifted 5 percent at a time
- All old Pods are stopped before any new one starts
Show answer
Answer: A. Two complete environments exist, one live and one idle, B. Traffic is switched from one environment to the other in one step, C. Rollback can be as simple as switching traffic back
Blue/green trades extra capacity for a clean cutover and fast rollback. Percentage steps describe canary; stopping everything first describes recreate.
True or false: the Recreate strategy avoids downtime because it starts new Pods before stopping old ones.
Show answer
Answer: False
Recreate stops all old Pods first, so there is a gap with no running version. Starting new ones before stopping old ones is what rolling update and blue/green do.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
