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

Multiple deployments/stses auto scalating to one by http add on trigger #1081

Open
metsoft68 opened this issue Jul 3, 2024 · 2 comments
Open

Comments

@metsoft68
Copy link

metsoft68 commented Jul 3, 2024

Proposal

Adding support for multiple scaleTargetRef entries in the HTTP scale object manifest. Only one of these targets should be flagged as the primary, which the HTTP interceptor will proxy the request to. The non-primary targets should simply scale to 1. If a scaleTargetRef is referenced by another HTTP scale object, they should not conflict with each other.

Use-Case

I have a testing/staging environment with around 20 microservices, 3 of which have ingress controllers that accept HTTP requests from outside. My goal is to scale all deployments, stateful sets, etc., to 1 based on the very first request that comes in via any of those 3 applications, using an HTTP scale object. This approach can significantly reduce costs for my test environments. Additionally, all pods should scale to 0 if none of those 3 ingresses have any traffic.

Is this a feature you are interested in implementing yourself?

No

Anything else?

keep up rocking! :)

@EinavDanielDX
Copy link

I have a similar use case, this feature would be most useful.

@nyobe
Copy link

nyobe commented Sep 29, 2024

I think that if #1083 were fixed this would be possible by creating multiple ScaledObjects that reference the same HTTPScaledObject trigger.

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

No branches or pull requests

3 participants