-
Notifications
You must be signed in to change notification settings - Fork 860
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
Kafdrop connection to an kafka servier with just SSL (not SASL) does not work #201
Comments
I found that, to fix it all that I had to do was to
and I could simplify the kafka.properties to
|
Hello @krishna-prasad-s , Wanted one quick info. How are you able to pass your truststore file via argument. The truststore file is pretty huge and whenever i run based on the docker run command,.. i get bin/docker : too many arguments error |
if your file is too big why don't you create your own docker image using this as the base image and packaging your trust store. |
Hi there, Here the error:
Here my helm custom helm values: service:
annotations: {}
type: ClusterIP
port: 9000
nodePort: ""
kafka:
brokerConnect: kafka-kafka-bootstrap:9093
jvm:
opts: "-Xms32M -Xmx64M"
image:
tag: 3.27.0 |
Yeah tried that now. thanks ! |
Works for me when I added without having to rebuild the source code. security.protocol=SSL what you have seems to give a warning ssl.security.protocol=SSL 2021-12-07 22:38:36.939 WARN 1 [ main] o.a.k.c.c.AbstractConfig : The configuration 'ssl.security.protocol' was supplied but isn't a known config. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is still relevant to us and a fix is available in #202. Can you please look into that PR and merge it in? That way, we can use the standard Kafdrop image instead of having to maintain our own one. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
In the readme its described as its working, but when I provide the required details. It throws an exception (mainly because the server refuses)
the docker command
the exception
The text was updated successfully, but these errors were encountered: