What does the maxUnavailable: 25% setting signify?

What does the maxUnavailable: 25% setting signify?

• A. Up to 25% of Pods can be unavailable during the update
• B. All pods must be available during update
• C. It limits the number of replicas to 25
• D. It sets 25% of nodes to be cordoned during update

Answer: (A)

maxUnavailable controls how many pods can be not ready during a rolling update. With 25%, the update may have up to a quarter of the desired pods unavailable at any moment, while the rest stay serving traffic. For example, with 8 replicas you could have up to 2 pods updating at once; with 3 replicas you’d typically allow about 1 to be unavailable. This setting is about pod readiness during the update, not about limiting replicas or cordoning nodes.

maxUnavailable controls how many pods can be not ready during a rolling update. With 25%, the update may have up to a quarter of the desired pods unavailable at any moment, while the rest stay serving traffic. For example, with 8 replicas you could have up to 2 pods updating at once; with 3 replicas you’d typically allow about 1 to be unavailable. This setting is about pod readiness during the update, not about limiting replicas or cordoning nodes.