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
Move activator count computation into KPA #11375
Move activator count computation into KPA #11375
Conversation
/hold For a bit of discussion I just posted #11373 (comment) |
Codecov Report
@@ Coverage Diff @@
## main #11375 +/- ##
==========================================
+ Coverage 87.68% 87.71% +0.02%
==========================================
Files 191 191
Lines 9219 9224 +5
==========================================
+ Hits 8084 8091 +7
+ Misses 880 879 -1
+ Partials 255 254 -1
Continue to review full report at Codecov.
|
18ab385
to
a99fc07
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.
/lgtm
/unhold |
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.
pretty much looks great to me! I might well be wrong, but if Im reading kpa_test right I think we're missing coverage for the two cases (0, -1) where TargetBurstCapacity isn't a positive number, (if so) worth adding those?
Thanks @julz. Added a targeted unit test just for the computation function to make the cases a bit clearer. |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: julz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #11373
Proposed Changes
See the above issue for further infromation. Changes the default to 2 rather than all, which should be correct in most cases anyway as the autoscaler would immediately set it to 2 in most cases anyway.
Release Note
/assign @julz @vagababov