-
Notifications
You must be signed in to change notification settings - Fork 96
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
Routing table is not synchronized #744
Comments
@t0rr3sp3dr0 can you please have a look please? |
Hey @Mickeyrourkeske, can you share your HTTPScaledObject definition and the full logs of the operator, scaler, and interceptor? Can you send me the output of The log message you are seeing is normal and doesn't indicate a problem. When the interceptor starts, it takes a while for the routing table to be synced. The first few readiness probes fail, logging the error that caused the failures. If there is a problem and the routing table never gets synced, the pod would never become ready and wouldn't receive any traffic. Otherwise, the pod becomes ready no more error logs should be seen from that point onwards. |
Hey, thanks for your reply. I think you are right. There seems to be some other problem. I don't know how I missed the errors last time. HTTPScaledObject
keda-admission-webhooks
keda-operator
keda-operator-metrics-apiserver
keda-add-ons-http-controller-manager
keda-add-ons-http-external-scaler
keda-add-ons-http-interceptor
kubectl get all -n keda
Thanks for looking into this |
The errors you are getting on the operator and scaler logs are expected because of #718, but there should be no impact on the autoscaling behaviour of the add-on. What is the response, including headers, you get when sending the request to the interceptor using the host and path defined on the HTTPScaledObject? Can you send me the command you are using? |
After trying out the example which worked, I found out that my ingress was wrong. It was still pointing to my service and not to the keda-add-ons-http-interceptor-proxy. Also it is worth noticing that the ingress needs to be in the same namespace as the keda-add-ons-http-interceptor-proxy Tank you very much for your help |
Report
Installed keda-core and the http-add-on and created a scaled object.
The deployment is scaled to 0, but never scaled up.
After looking around I found an error in the keda-add-ons-http-interceptor
"msg":"health check function failed","error":"table has not synced","errorVerbose":"table has not synced...
Expected Behavior
The deployment get scaled to 1
Actual Behavior
The deployment is never scaled to 1
Steps to Reproduce the Problem
Logs from KEDA HTTP operator
HTTP Add-on Version
0.5.0
Kubernetes Version
1.26
Platform
Other
Anything else?
No response
The text was updated successfully, but these errors were encountered: