Sameer Joshi

Hi @dttung2905 , Please see answers inline Has it setup been working well for you before you encounter this problem? Or this is the first time this scaler has been...

Following is the analysis from AWS MSK team for the issue. They see this as a problem in Keda scaler. The issue is mainly new apache kafka scaler keep on...

> Been a while since I worked with Kafka, I made the initial commit for the scaler. > > If it's an issue with rotating credentials I think it would...

> > The behaviour on MSK side is that the failure is happening in the authorization flow, and not the authentication flow. This was hard to reproduce. However, when we...

I see AWS has released the signer https://github.com/aws/aws-msk-iam-sasl-signer-go . This signer can be integrated with IBM sarama library. The signer implements the interface necessary for SASL OAUTHBEARER authentication. This means...

@adrien-f I thought we were discussing the idea of modifying the existing Kafka scaler based on sarama library than fixing the issue with the experimental scaler based on segment-io library.

@adrien-f Following is the original scaler based on sarama library: https://github.com/kedacore/keda/blob/80806a73218e7d128bd25945f573c2a91316d1d3/pkg/scalers/kafka_scaler.go and the experimental scaler is this : https://github.com/kedacore/keda/blob/80806a73218e7d128bd25945f573c2a91316d1d3/pkg/scalers/apache_kafka_scaler.go The thing mentioned in the above comments suggests that the original...