Trying to integrate with Azure Managed Prometheus but getting Unauthorised issue about keda

[JorTurFer]

Hello!
Those envs are automatically set by the workload identity webhook when a pod whose service account has the annotation is scheduled. That's a component that has to be present in your cluster.

Could you confirm that you have installed it?
It is done by the --enable-workload-identity argument during cluster update

If you prefer to install if by yourself, you can do it following their guide: https://azure.github.io/azure-workload-identity/docs/installation.html

[KasyapG]

@JorTurFer , We have enabled the workload identity and did a restart of Keda operator as well using the document provided, still see 401 unauthorized in the logs to connect to, so could help us understand the what else could be the issue. I also provided the scaledobeject yaml

[JorTurFer]

Oh, I have just noticed that you are using KEDA v2.10.0. Could you confirm this? The support for Azure managed Prometheus was added in v2.11 so maybe you have to upgrade KEDA

[KasyapG]

Hi @JorTurFer ,

As per the Microsoft documentation it says 2.10 is the required version, so we have upgraded to 2.10

Also we tried using bearer token type as authmode in the scaled object (shown below) as per the documentation "https://keda.sh/docs/2.13/scalers/prometheus/", but still facing an unauthorized issue.

Is there anything else should we look in to.

Regards,
Kasyap G

[JorTurFer]

Do you still see the same error about missing header? You configuration looks good, so I'd like to know if you still get the same error or it has changed

[stale]

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.