Which deployment strategy is designed to minimize downtime during updates by controlling the number of pods upgraded at a time?

Which deployment strategy is designed to minimize downtime during updates by controlling the number of pods upgraded at a time?

• A. Canary with traffic shifting
• B. Blue-Green with separate environments
• C. RollingUpdate with maxSurge and maxUnavailable
• D. Recreate

Answer: (C)

Controlling how many pods are updated at once is the essence of the rolling update approach. By configuring maxSurge and maxUnavailable, you limit how many extra pods can be created during the rollout and how many pods may be unavailable at any moment. This lets the system upgrade a subset of pods while keeping the rest serving traffic, proceeding in batches rather than all at once and thus minimizing downtime. The other strategies focus on testing (Canary), switching between entire environments (Blue-Green), or tearing down everything before starting anew (Recreate), which don’t inherently manage pod-by-pod upgrade concurrency.

Controlling how many pods are updated at once is the essence of the rolling update approach. By configuring maxSurge and maxUnavailable, you limit how many extra pods can be created during the rollout and how many pods may be unavailable at any moment. This lets the system upgrade a subset of pods while keeping the rest serving traffic, proceeding in batches rather than all at once and thus minimizing downtime. The other strategies focus on testing (Canary), switching between entire environments (Blue-Green), or tearing down everything before starting anew (Recreate), which don’t inherently manage pod-by-pod upgrade concurrency.