Set a Rolling Update Budget
Calculate a Deployment rolling update strategy that balances speed and minimum available capacity.
before-after stepper now-you-try The profile API runs 10 replicas. During a release, the business wants at least 9 replicas available and can tolerate up to 2 extra temporary Pods if the cluster has room. Translate the availability promise into maxUnavailable and the spare-capacity promise into maxSurge. The common trap is treating rolling update settings as speed knobs only. If maxUnavailable allows too much loss or maxSurge assumes capacity that does not exist, the rollout either hurts users or stalls. Step 1 Desired replicas = 10. Minimum acceptable available = 9. Therefore at most 1 Pod may be unavailable during the…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in