HTTP Trigger not scaling up

[rahulpr17]

I am trying to deploy an HTTP Trigger to keda. I have installed Osiris components for the same. It helped me to scale to zero when no request is coming, but it is not scaling up from 1 instance. I have removed all replica-constraints from deploy.yaml file still no effects. Can you help me with any supportive links?

[asavaritayal]

@asavaritayal to find the right place for the issue. This looks like an Osiris issue.

[rahulpr17]

Thanks for looking into the issue. Can you please confirm if it is an issue with Osiris? I have been trying from days to test this and no luck on autoscaling Http Trigger. But Queue trigger is working without any issue.
Also please let us know if Keda support for TimeTrigger will be available in near future?

[yaron2]

I assume by HTTP Trigger you mean an HTTP Azure Function?

The scale to/from zero you are referring to is only achieved via Osiris, KEDA is not in play here at all, and thus this has to be a (potential) Osiris issue.

You can look for Osiris logs for the different Osiris components under the osiris-system namespace to help you understand if something went wrong.

[rahulpr17]

Thank you for the response. I have raised a bug to the osiris team and checking with them.

[aletc1]

Keda team, please review this:
deislabs/osiris#34

The issue is with the func toolset that has a missing configuration. e.g if you add this then everything work as expected:

"osiris.deislabs.io/loadBalancerHostname": "locahost"

In my case, localhost was the loadbalancer (Docker Desktop/Kubernetes) but it should be the actual balancer DNS name.

[tomkerkhove]

I presume this issue can be closed as it's not related to KEDA.

Feel free to re-open in case it's required.