Skip to content

Allow scaling (1->n) based on CPU and memory metrics but keep activating (0->1) on HTTP requests #1278

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

Open
AlphaNam opened this issue Apr 1, 2025 · 1 comment

Comments

@AlphaNam
Copy link

AlphaNam commented Apr 1, 2025

Hello,

We would like to activate a deployment (scale from 0 to 1) using HTTP metrics and scale up/down (1 to n, or n to 1) based on other types of metrics such as CPU or memory utilization. We could not find any way to achieve this.

We tried to use HPA ownership transfer using an HTTPScaledObject as described in Keda documentation : https://keda.sh/docs/2.16/concepts/scaling-deployments/#transferring-ownership-of-an-existing-hpa
We tried to add the key "advanced" in the HTTPScaledObject but it looks like it is not supported yet.

Regards,

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

2 participants