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

Align MIG update policy with GKE (maxSurge=1 maxUnavailable=0) #32

Closed
jeffmccune opened this issue Dec 23, 2020 · 0 comments · Fixed by #34
Closed

Align MIG update policy with GKE (maxSurge=1 maxUnavailable=0) #32

jeffmccune opened this issue Dec 23, 2020 · 0 comments · Fixed by #34
Milestone

Comments

@jeffmccune
Copy link
Member

The update policy of max_unavailable_fixed = 1 could result in capacity being reduced during a rolling update, causing disruption. If the autoscaler has a target size of 6, then one instance may be removed while the replacement instance is still in the process of being created.

The default behavior should align with GKE, see Determining your optimal surge configuration

All new node pools are automatically configured to use surge upgrades (maxSurge=1 maxUnavailable=0).

@jeffmccune jeffmccune changed the title Align MIG update policy with GKE Align MIG update policy with GKE (maxSurge=1 maxUnavailable=0) Dec 23, 2020
@jeffmccune jeffmccune added this to the 3.x milestone Dec 24, 2020
@jeffmccune jeffmccune modified the milestones: 3.x, 3.2.0 Dec 24, 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 a pull request may close this issue.

1 participant