Repository navigation
Fix KPA initial scale exceeding max scale - #16710
jahnavigajjala-3 wants to merge 5 commits into
Conversation
|
Hi @jahnavigajjala-3. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jahnavigajjala-3 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #16710 +/- ##
==========================================
- Coverage 80.36% 80.34% -0.02%
==========================================
Files 217 217
Lines 13560 13564 +4
==========================================
+ Hits 10897 10898 +1
- Misses 2301 2305 +4
+ Partials 362 361 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Fixes #16709
Proposed Changes
maxScalewhenmaxScaleis positive, preventing the KPA scaler from exceeding the configured maximum during initial scaling.maxScale = 0), min/max-scale interactions, unreachable revisions, and activation behavior.Release Note