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

Support multiple scaleTargetRefs or support Ingress path #1175

Open
ppawiggers opened this issue Oct 22, 2024 · 1 comment
Open

Support multiple scaleTargetRefs or support Ingress path #1175

ppawiggers opened this issue Oct 22, 2024 · 1 comment
Labels
stale All issues that are marked as stale due to inactivity

Comments

@ppawiggers
Copy link

Proposal

KEDA should be able to scale multiple scaleTargetRefs.

Or KEDA proxy should be able to select the corresponding Deployment based on Ingress path.

Use-Case

I have two Deployments: a and b. Both are accessible through Ingress. They share a hostname example.com and are routed on path: /a and /b.

I want to scale both Deployments when a request comes in, but it seems KEDA proxy cannot distinguish on path, it just randomly picks a HTTPScaledObject with the corresponding hostname and scales that Deployment.

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response

@ppawiggers ppawiggers changed the title Support multiple scaleTargetRefs or support path Support multiple scaleTargetRefs or support Ingress path Oct 22, 2024
@zroubalik zroubalik transferred this issue from kedacore/keda Oct 23, 2024
Copy link

stale bot commented Dec 23, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale All issues that are marked as stale due to inactivity
Projects
Status: To Triage
Development

No branches or pull requests

1 participant