How to work with Keda using Azure pod identity

Question

I'm trying to use pod identity in conjunction with KEDA to access some Azure resources, Azure Service Bus & Keyvaults to be precise.

I noticed the aadpodbinding should be set when deploying the operator according to these instructions. I am probably misinterpreting the instructions because the way I read it is that I need to have a single aadpodbinding ie. have some sort of cluster-wide "keda-identity"?

I wonder how I could utilize pod identity in my scenario: I want to have a separate identity for every solution running in my AKS cluster. These identities will provide the solutions with access to Azure resources and then I want to use those identities to provide the authentication as well for KEDA. I do not want a shared identity to access multiple resources on my subscription.

Surely this is possible and I am misinterpreting the instructions somehow (not being a native English speaker)?

Answer 1

You can add pod identity binding using the command:

helm install keda kedacore/keda --set podIdentity.activeDirectory.identity=app-autoscaler --namespace keda

But this didnt make my day to successfully scale the KEDA scaler using pod identity trigger auth

tried opening a new query here to try to get it scaled using pod identity trigger