-
Notifications
You must be signed in to change notification settings - Fork 90
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 HTTPScaledObject scoped timeout #813
Comments
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. |
This issue has been automatically closed due to inactivity. |
Hi, is this expected in future releases? We're using shared k8s cluster so it would be easier to use scoped timeout than asking platform team to come with values that fit all teams sharing the cluster. Also what kinds of timeouts is this expected to support? |
No, this has been closed automatically due to inactivity. Are you willing to contribute with it?
The original proposal was to override the "cold start timeout" |
Sorry, I don't have any experience with go and this doesn't seem like easy task to start.
Ok, we got API that can take long to answer so I was looking for something to override the |
I've checked and I guess that we could configure all the timeouts at same place from the HTTPScaledObject, so maybe could support all of them. |
Having something like this would be great. We were trying to deploy LLMs this way on a cluster, having at most a few requests pending before adding new resources. |
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. |
I would be willing to have a closer look at this but I have literally no idea where to start (and no experience whatsoever with coding for keda). Any suggestion or example of a variable that has similar behaviors where I could have a look to start it ? |
I found a way to change the default timeout of keda http addon, while installing http addon via the helm we can change the default value from values.yaml file. interceptor: |
Proposal
Currently, there is a timeout configuration for setting the request timeout.
Allowing HTTPScaledObjects to override the timeout for specific route can help to users who have some slow routes but they prefer to not increase the global timeout for all the routes just due to some of them
Use-Case
No response
Is this a feature you are interested in implementing yourself?
Maybe
Anything else?
No response
The text was updated successfully, but these errors were encountered: