Skip to content

autoscaler: ignore ScaleDownDelay if not reachable #15831

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

Merged

Conversation

scottjmaddox
Copy link
Contributor

@scottjmaddox scottjmaddox commented Apr 4, 2025

Proposed Changes

  • autoscaler: ignore ScaleDownDelay if not reachable
    • addresses an issue we noticed where old revisions would hang around for the full scale down delay even if zero traffic is being directed to them, resulting in unnecessary resource utilization (especially if the scale down delay is large)

Release Note

autoscaling: ignore ScaleDownDelay if the revision is not reachable

Copy link

linux-foundation-easycla bot commented Apr 4, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: scottjmaddox / name: Scott J Maddox (e2d98b1)
  • ✅ login: dprotaso / name: Dave Protasowski (ec2d263)

@knative-prow knative-prow bot requested review from dprotaso and skonto April 4, 2025 19:48
@knative-prow knative-prow bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 4, 2025
Copy link

knative-prow bot commented Apr 4, 2025

Hi @scottjmaddox. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions 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.

@dprotaso
Copy link
Member

dprotaso commented Apr 4, 2025

/ok-to-test

@knative-prow knative-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 4, 2025
Copy link

codecov bot commented Apr 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.04%. Comparing base (3c3e59c) to head (ec2d263).
Report is 9 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #15831   +/-   ##
=======================================
  Coverage   75.04%   75.04%           
=======================================
  Files         222      222           
  Lines       18074    18074           
=======================================
  Hits        13563    13563           
+ Misses       4160     4159    -1     
- Partials      351      352    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@scottjmaddox
Copy link
Contributor Author

@dprotaso Any action needed from me on this? Thanks.

@skonto
Copy link
Contributor

skonto commented Apr 10, 2025

Hi there are some code style issues.

@dprotaso
Copy link
Member

/override "codecov/project"

tracking that as a separate issue - knative/infra#634

Ran gofumpt on the file - thanks @scottjmaddox

/lgtm
/approve

Copy link

knative-prow bot commented Apr 13, 2025

@dprotaso: Overrode contexts on behalf of dprotaso: codecov/project

In response to this:

/override "codecov/project"

tracking that as a separate issue - knative/infra#634

Ran gofumpt on the file - thanks @scottjmaddox

/lgtm
/approve

Instructions 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.

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Apr 13, 2025
Copy link

knative-prow bot commented Apr 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, scottjmaddox

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 13, 2025
@knative-prow knative-prow bot merged commit 3d830a0 into knative:main Apr 13, 2025
68 of 69 checks passed
Copy link

@jyono jyono left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants