-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ScaledObject with Camel K Integration custom resource is broken #4695
Comments
Based on the code, this shouldn't happen but maybe we have missed something |
I can't reproduce the bug. The only way to reproduce the issue has been adding a section in the BTW, how are you deploying KEDA? Are you using the open source project or the OpenShift custom metrics server? I don't recognize the folders in the error logs, the errors say:
and it should be:
|
We deployed KEDA from the Red Hat operator catalog, exact version is: "Custom Metrics Autoscaler The full
We already tried to set this in the ClusterTriggerAuthentication:
But that didn't help. Our OpenShift cluster runs on-premise, so we do not use any public cloud podintetity provider. |
@zroubalik , FYI. |
This is a very strange and weird issue. I am not aware of anything in the build process that could cause this, @joelsmith FYI. I see a configuration option that doesn't make sense for Prometheus: Could you please try to use TriggerAuthentication instead of ClusterTriggerAuthentication? If it doesn't help, could you please try to use upstream KEDA 2.10.1? Just install it via yaml method. |
I'm tracking this on Red Hat's side as https://issues.redhat.com/browse/OCPBUGS-15274 and I will see if I can figure out what's going on, whether it's specific to Red Hat's build / deploy config or not. |
"I see a configuration option that doesn't make sense for Prometheus: Fair point, I accidently left the "Could you please try to use TriggerAuthentication instead of ClusterTriggerAuthentication?" I tried it, unfortunately it didn't help either.
"If it doesn't help, could you please try to use upstream KEDA 2.10.1? Just install it via yaml method." Thanks for the suggestion, I managed to uninstall the Red Hat Custom Metrics Autoscaler operator, and install the upstream KEDA 2.10.1 from yaml. Surprisingly (or not surprisingly) the error remained the same, here is the new operator log for my latest attempt:
|
I think I have figured this out. The new code which gives this error is buggy in that it checks for the empty string instead of "none". I'll post a PR shortly. Edit: PR posted here: #4748 |
Report
We recently updated to Keda 2.10.1, from 2.8.2, and our ScaledObject configuration is now not working correctly. Here is the ScaledObject resource:
And the reffered ClusterTriggerAuthentication:
As you can see, the scaleTargetRef is the Apache Camel K operator's Integration custom resource type, with only one promethes type trigger and ClusterrTriggerAuthentication to the OpenShift monitoring thanos-querier endpoint. The issue is that the HorizontalPodAutoscaler object did not created for this ScaledObject as the status shows. The same ScaledObject configuration with a scaleTargetRef to a standard Deployment still works though.
Expected Behavior
The HPA should be created for the Camel K Integration custom resource with a custom prometheus metrics scaler.
Actual Behavior
The HPA did not created for the Camel K Integration custom resource with a custom prometheus metrics scaler.
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.10.1
Kubernetes Version
1.25
Platform
Red Hat OpenShift
Scaler Details
Prometheus
Anything else?
No response
The text was updated successfully, but these errors were encountered: