Which deployment strategy settings control how many pods can be unavailable or created during a rollout to minimize downtime?

Which deployment strategy settings control how many pods can be unavailable or created during a rollout to minimize downtime?

• A. Recreate settings.
• B. RollingUpdate settings (maxUnavailable, maxSurge).
• C. Blue/Green settings.
• D. Canary settings.

Answer: (B)

During a rollout, the rolling update strategy controls how many pods can be unavailable or created at once to keep the service up. The knobs you adjust are maxUnavailable and maxSurge. maxUnavailable limits how many pods can be offline during the update, helping control downtime. maxSurge allows extra pods to be created above the desired count, giving capacity to handle traffic while new pods start. Together, these settings tune the pace of the rollout and minimize downtime. Other approaches like Recreate terminate old pods before new ones start, causing downtime; Blue/Green and Canary involve traffic switching or staged releases but do not directly specify per-update pod counts in the same way.

During a rollout, the rolling update strategy controls how many pods can be unavailable or created at once to keep the service up. The knobs you adjust are maxUnavailable and maxSurge. maxUnavailable limits how many pods can be offline during the update, helping control downtime. maxSurge allows extra pods to be created above the desired count, giving capacity to handle traffic while new pods start. Together, these settings tune the pace of the rollout and minimize downtime. Other approaches like Recreate terminate old pods before new ones start, causing downtime; Blue/Green and Canary involve traffic switching or staged releases but do not directly specify per-update pod counts in the same way.