Vighnesh Shenoy

After going through the docs for [azure-event-hubs-go/v3](https://pkg.go.dev/github.com/Azure/azure-event-hubs-go/v3), it relies on the [azure-amqp-common-go/sas](https://pkg.go.dev/github.com/Azure/[email protected]/sas) package for a SAS token provider which requires either providing the key name & value, or a connection...

Hi, @kedacore/keda-maintainers. I am reading a bit about Spiffe currently, and willing to take a stab at this if it's alright? I'll try to come up with a proposal and...

@tomkerkhove @JorTurFer This is actually regarding a KEDA installation using the AKS add-on. You can ignore the missing webhook configuration error, that's an error in the add-on Helm chart that...

There are two replicas for the metric server. One of them is able to connect successfully, the other one is continuously timing out. We had multiple clusters face this issue....

Besides the missing webhook configuration, I don't think we were seeing any other errors in the operator pod. Plus, one of the metric servers did connect successfully. Correct me if...

I think the AKS system pods were being throttled due to the size of the system pool nodes being small. @sktemkar increased the nodes size as well as added the...

@krishna-kariya PTAL.

> WDYT @v-shenoy ? Yeah, sounds good. Are we planning to add this only for Event Hub, or all Azure scalers @JorTurFer?

> I guess that this is interesting for all azure scalers, isn't? It is. I asked because the issue is titled for Event Hub.

> @v-shenoy , were you involved with aad-pod-identity team? Do you have any suggestion? The add-pod-identity token provider is correctly created because it says timeout and not error on it...