Skip to content
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

Disable metrics-based autoscaling by default when scaleUpTriggers are enabled #391

Merged
merged 1 commit into from
Mar 14, 2021

Conversation

mumoshu
Copy link
Collaborator

@mumoshu mumoshu commented Mar 14, 2021

Relates to #379 (comment)
Relates to #377 (comment)

When you defined HRA.Spec.ScaleUpTriggers[] but HRA.Spec.Metrics[], the HRA controller will now enable ScaleUpTriggers alone and insteaed of automatically enabling TotalNumberOfQueuedAndInProgressWorkflowRuns. This allows you to use ScaleUpTriggers alone, so that the autoscaling is done without calling GitHub API at all, which should grealy decrease the change of GitHub API calls get rate-limited.

@mumoshu mumoshu force-pushed the scale-up-trigger-only-scaling branch 3 times, most recently from c42a5a5 to 48df001 Compare March 14, 2021 01:51
… enabled

Relates to #379 (comment)
Relates to #377 (comment)

When you defined HRA.Spec.ScaleUpTriggers[] but HRA.Spec.Metrics[], the HRA controller will now enable ScaleUpTriggers alone and insteaed of automatically enabling TotalNumberOfQueuedAndInProgressWorkflowRuns. This allows you to use ScaleUpTriggers alone, so that the autoscaling is done without calling GitHub API at all, which should grealy decrease the change of GitHub API calls get rate-limited.
@mumoshu mumoshu force-pushed the scale-up-trigger-only-scaling branch from 48df001 to 9a1c514 Compare March 14, 2021 01:59
@mumoshu mumoshu merged commit 5530030 into master Mar 14, 2021
@mumoshu mumoshu deleted the scale-up-trigger-only-scaling branch March 14, 2021 02:03
@Puneeth-n
Copy link
Contributor

@mumoshu how does scale down happen when we use Github Webhook based scaling and no metrics?

@mumoshu
Copy link
Collaborator Author

mumoshu commented Mar 15, 2021

@Puneeth-n Each scaleUpTrigger expires after the configured duration passed. Let's say duration was 5m(5 minutes), RD's desired replicas increases by the configured replica(s) for 5 minutes. After 5 minutes the RD's desired replicas decreases by 1.

You'll also find https://github.com/summerwind/actions-runner-controller#faster-autoscaling-with-github-webhook useful!

@Puneeth-n
Copy link
Contributor

@mumoshu Thanks for clarifying. I didn't know it would scale down as well after the "duration"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants