The maxSurge setting allows Kubernetes to create additional Pods over the desired replica count during a rolling update, while maxUnavailable limits how many of the desired Pods may be taken offline.
With a desired replica count of 4 and maxSurge: 2, Kubernetes may temporarily run up to 2 extra Pods (4 + 2 = 6) to bring up new versions before stopping the old ones. The maxUnavailable: 1 constraint only limits how many Pods may be out of service at any moment; it does not increase the total Pod count. Therefore, the greatest possible number of concurrently running Pods during the update is 6. All other answer choices either ignore the surge allowance (4), mis-apply the unavailability limit (5), or count both the surge and the unavailable Pods as additional replicas (7).
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the purpose of maxSurge in Kubernetes?
Open an interactive chat with Bash
How does maxUnavailable affect a rolling update in Kubernetes?
Open an interactive chat with Bash
How do maxSurge and maxUnavailable work together during a Kubernetes Deployment update?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Automation, Orchestration, and Scripting
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access