-
Notifications
You must be signed in to change notification settings - Fork 26
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
✨Autoscaling: add a delay before draining a node #5843
✨Autoscaling: add a delay before draining a node #5843
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5843 +/- ##
=========================================
+ Coverage 84.5% 87.6% +3.1%
=========================================
Files 10 1367 +1357
Lines 214 56790 +56576
Branches 25 1284 +1259
=========================================
+ Hits 181 49801 +49620
- Misses 23 6715 +6692
- Partials 10 274 +264
Flags with carried forward coverage won't be shown. Click here to find out more.
|
021b977
to
f6cead9
Compare
ee62f19
to
5ac56c4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool!
5ac56c4
to
5cffffd
Compare
Quality Gate passedIssues Measures |
What do these changes do?
This PR adds a delay (
EC2_INSTANCES_TIME_BEFORE_DRAINING
) before draining active nodes (e.g. EC2 in the cluster that are available to run services) so that in case a dynamic sidecar would fail on start it has time to restart and is not rejected.driving tests:
bonus:
Related issue/s
How to test
Dev-ops checklist
EC2_INSTANCES_TIME_BEFORE_DRAINING
andWORKERS_EC2_INSTANCES_TIME_BEFORE_DRAINING
that take in a timedelta between 10 seconds and 1 minute (auto-capped)