Skip to content
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

Kafka/SASL missing documentation and uses confusing verbiage #1217

Closed
cbuckley01 opened this issue May 14, 2021 · 5 comments
Closed

Kafka/SASL missing documentation and uses confusing verbiage #1217

cbuckley01 opened this issue May 14, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@cbuckley01
Copy link
Contributor

cbuckley01 commented May 14, 2021

Config validation for Kafka/SAML is broken, when configuring just a password the contoller throws the following error:

{"level":"error","ts":1621011775.476398,"logger":"argo-events.eventsource-controller","caller":"eventsource/controller.go:81","msg":"validation error","namespace":"argo-events","eventSource":"kafka","error":"invalid sasl config, please configure either User, and/or Password"

This config works:

     sasl:
        mechanism: PLAIN
        password:
          key: password
          name: my-user
        user:
          key: user
          name: my-user

This will not:

     sasl:
        mechanism: PLAIN
        password:
          key: password
          name: my-user
@cbuckley01 cbuckley01 added the bug Something isn't working label May 14, 2021
@whynowy
Copy link
Member

whynowy commented May 17, 2021

Forgive my poor Kafka knowledge, is password only config allowed? @joshuajorel @cbuckley01

@cbuckley01
Copy link
Contributor Author

Right, that way be true, sorry, I might have been a bit confused by the error message

@joshuajorel
Copy link
Contributor

@whynowy I'm not aware that you should be able to configure password only since the user value is usually used for ACL. I think he's referring to if you can reference the same field for the secret to contain the username and password. Should this be the implementation?

@cbuckley01 User and Password values should be in two separate fields in the Secret object.

@cbuckley01
Copy link
Contributor Author

Right, I have re-titled this issue with the root issue. I will hopefully get you guys a PR today making things a bit more clear/consistent with TLS wording and add an examples to help clarify this for future users.

@cbuckley01 cbuckley01 changed the title Kafka/SASL password only configuration doesn't work Kafka/SASL missing documentation and uses confusing verbiage May 18, 2021
cbuckley01 pushed a commit to cbuckley01/argo-events that referenced this issue May 18, 2021
… for Kafka/SASL argoproj#1217

Signed-off-by: Christopher Buckley <cbuckley@propointglobal.com>
cbuckley01 pushed a commit to cbuckley01/argo-events that referenced this issue May 18, 2021
… for Kafka/SASL argoproj#1217

Signed-off-by: Christopher Buckley <cbuckley@propointglobal.com>
whynowy pushed a commit that referenced this issue May 18, 2021
* Fix: Clean up descriptions, add example and rename configration names for Kafka/SASL #1217

Signed-off-by: Christopher Buckley <cbuckley@propointglobal.com>
@whynowy
Copy link
Member

whynowy commented May 20, 2021

#1220

@whynowy whynowy closed this as completed May 20, 2021
juliev0 pushed a commit to juliev0/argo-events that referenced this issue Mar 29, 2022
* Fix: Clean up descriptions, add example and rename configration names for Kafka/SASL argoproj#1217

Signed-off-by: Christopher Buckley <cbuckley@propointglobal.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants