How do maxSurge and maxUnavailable influence rolling updates in a Deployment?

Prepare for the Red Hat Openshift Developer EX288 Exam. Study with comprehensive quizzes and flashcards. Each question includes hints and explanations to enhance your understanding. Ace your exam with confidence!

Multiple Choice

How do maxSurge and maxUnavailable influence rolling updates in a Deployment?

During a rolling update, maxSurge and maxUnavailable control how the upgrade proceeds by shaping the number of pods that can run during the update and how many can be down at any moment. maxSurge defines how many extra pods may be created above the desired replica count while the upgrade happens. This lets the new version come up in parallel with the old one. maxUnavailable specifies how many pods are allowed to be unavailable (not ready) during the update, preventing too many pods from being down at once and helping maintain service availability. Both values can be a fixed number or a percentage of the desired replicas, so you can scale the behavior to fit your cluster size. For example, with a desired count of five, a surge of up to two and an unavailable limit of one means up to seven pods can exist during the update, and at most one of them may be unavailable at any time, keeping the rest serving traffic. In short, these settings directly govern how many pods are created beyond the target and how many may be down during the rollout, balancing update speed with availability. They aren’t about resource limits, readiness probes, or image pull policies.

During a rolling update, maxSurge and maxUnavailable control how the upgrade proceeds by shaping the number of pods that can run during the update and how many can be down at any moment. maxSurge defines how many extra pods may be created above the desired replica count while the upgrade happens. This lets the new version come up in parallel with the old one. maxUnavailable specifies how many pods are allowed to be unavailable (not ready) during the update, preventing too many pods from being down at once and helping maintain service availability.

Both values can be a fixed number or a percentage of the desired replicas, so you can scale the behavior to fit your cluster size. For example, with a desired count of five, a surge of up to two and an unavailable limit of one means up to seven pods can exist during the update, and at most one of them may be unavailable at any time, keeping the rest serving traffic.

In short, these settings directly govern how many pods are created beyond the target and how many may be down during the rollout, balancing update speed with availability. They aren’t about resource limits, readiness probes, or image pull policies.

More practice questions