Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update RollingUpdate strategy to allow 10% unavailable #805

Merged
merged 1 commit into from
Jan 29, 2020
Merged

Update RollingUpdate strategy to allow 10% unavailable #805

merged 1 commit into from
Jan 29, 2020

Conversation

gavinbunney
Copy link
Contributor

Description of changes:

This updates the RollingUpdate strategy to allow more pods to update simultaneously. When updating a reasonably sized cluster (~400 nodes), having a single pod update at a time takes an extremely long time.

The PR changes the update strategy to allow 10% unavailable. This aligns with the update strategy from kube-proxy (here)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Copy link
Contributor

@mogren mogren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @gavinbunney! Matching the kube-proxy setting makes sense to me.

Copy link
Contributor

@jaypipes jaypipes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, makes sense. Thanks @gavinbunney!

@jaypipes jaypipes merged commit 8a59da0 into aws:master Jan 29, 2020
mogren pushed a commit to mogren/amazon-vpc-cni-k8s that referenced this pull request Jan 31, 2020
jaypipes pushed a commit that referenced this pull request Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants