-
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
KEDA scaler error while init Azure Managed Prometheus client http transport #5006
Comments
Hello,
|
Hello,
|
Have you installed workload-identity webhook too? If you restart KEDA pods, do they have the envs? |
Great. Thanks for your support. After a restart the pods, the variables are loaded and KEDA started working.
|
Yeah, you're right. We merged this commit today for improving them: 089f22f |
BTW, I close the issue as it's already solved |
Report
KEDA scaler not scales with scaled object defined with trigger using workload identity for authentication for prometheus .
I'm following this KEDA Azure Monitor managed service for Prometheus.
KEDA operator error message log:
My scaler objects' definition is as below:
I'm install KEDA with the following command
Expected Behavior
The KEDA scaler should have worked fine with the assigned workload identity and access token to perform scaling
Actual Behavior
The KEDA operator could not be able to find the azure identity assigned and scaling fail
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.11.2
Kubernetes Version
1.26
Platform
Microsoft Azure
Scaler Details
Prometheus
Anything else?
No response
The text was updated successfully, but these errors were encountered: