-
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
GSSAPI sasl mechanism for Kafka scaler #4836
Comments
Hi, Can I assign this issue to you? Are you willing to help with this? |
Sarama definitely supports this. Just need to pass the right parameters to it. Thanks for the pointer on kafka-go. Didn't realize this was happening. |
AFIK there was some license issues in dependent libraries, and the PR for kafka-go segmentio/kafka-go#598 was stuck for so long. But we should probably include e2e case for this. |
My changes only consider the kafka scaler (based on sarama). The change is to collect relevant information in TriggerAuthentication and pass it along to sarama. Not sure about the e2e test - would require standing up kerberos infra as part of the test. I'd rather trust that sarama will do the right thing with inputs (it does). Unit tests ensure that correct values are passed along. |
For now, I can confirm that this works with keytab. Tested it with existing setup. |
Proposal
Support Kerberos authentication for Kafka scaler.
Use-Case
When target Kafka cluster requires SASL GSSAPI (Kerberos) authentication, currently there is no way to use Keda Kafka scaler.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
This is a repeat of ticket: GSSAPI sasl mechanism for Kafka scaler #857
Perhaps would be better to reopen the original ticket.
The text was updated successfully, but these errors were encountered: