-
Notifications
You must be signed in to change notification settings - Fork 27
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: Start using EBS-based EC2 buffers 🚨 #6143
✨Autoscaling: Start using EBS-based EC2 buffers 🚨 #6143
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6143 +/- ##
=========================================
+ Coverage 84.5% 88.1% +3.6%
=========================================
Files 10 1466 +1456
Lines 214 60912 +60698
Branches 25 1505 +1480
=========================================
+ Hits 181 53718 +53537
- Misses 23 6879 +6856
- Partials 10 315 +305
Flags with carried forward coverage won't be shown. Click here to find out more.
|
b5c0106
to
099a0d0
Compare
5f90278
to
9392bd0
Compare
2f52807
to
848309d
Compare
f8c68cc
to
1749ef3
Compare
1749ef3
to
4ac0ce7
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! This is the first time we start to use ssm
?
4ac0ce7
to
29106c1
Compare
Quality Gate passedIssues Measures |
What do these changes do?
In effect enable usage of EBS-based buffer machines (but still to be manually tested first of everything).
this was manually tested within AWS directly through /tests/manual and following README.md there.
Details:
--external-env
flagcloud-init status
test are deemed as broken and are auto-terminatedImportant Note:
This does not remove the old buffering system, but adds a new one that is currently not in use in any deployment.
Related issue/s
How to test
Dev-ops checklist