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

[eks deploy] Configurable rolling deployment for controlled roll out #91

Open
siarhei-karanets-epam opened this issue May 11, 2020 · 1 comment
Labels
enhancement New feature or request p:queued

Comments

@siarhei-karanets-epam
Copy link

The current approach with "kubergrunt eks deploy" causes downtime due to the fact that all nodes in a group receive drain simultaneously and all replicas of affected apps (the same for ingress controller, stateful sets, etc) start migration in the same time.
Need to improve the update procedure to avoid downtimes.

@yorinasub17 yorinasub17 added enhancement New feature or request help wanted labels May 11, 2020
@yorinasub17
Copy link
Contributor

Thanks for the highlighting this request! The current idea is to leverage PodDisruptionBudgets to avoid downtime in your apps. This is in general a better approach as it better respects the fine grained requirements of each app while balancing the speed of roll out over large clusters.

That said, having a configuration parameter to control how many nodes to drain and shutdown at a time in a rolling fashion is good to have.

@yorinasub17 yorinasub17 changed the title No downtime node upgrade Configurable rolling deployment Oct 21, 2021
@yorinasub17 yorinasub17 changed the title Configurable rolling deployment [eks deploy] Configurable rolling deployment for controlled roll out Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request p:queued
Projects
None yet
Development

No branches or pull requests

3 participants