-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add support for Kafka 0.10+ #268
Comments
I'm using it with Kafka 0.10.0.0 with no major problems. |
The wiki says as follows: Create a topic with optional topic configs (0.8.1.1 has different configs than 0.8.2+) Do these features work well with kafka 0.10? |
Has anyone enabled SSL inter broker communication / SASL_SSL auth with kafka in 0.10, and then tried to use kafka manager to manage the cluster? It doesn't seem to work for me. Is this something which needs adding? Edit - Just in case anyone else has this issue, the work around is to configure a plaintext listener for kafka-manager to connect to
If you then only allow your kafka manager server to connect to port 9094 via iptables or some other means, everything else is forced to use SSL while kafka manager can still connect. |
@KaimingWan I can state that topic deletion and marked for deletion works for Kafka 0.10.0.0. |
@falmp I have some problem in compiling kafka-manager. Would you mind sending me the code after compiling with sbt? My email is 344277934@qq.com or wan0573@gmail.com. Thanks! |
@KaimingWan What kind of problem? Anyway, sent you the link. |
@falmp I have solved the problem. Thanks anyway~ |
Hi all! |
@freemanlutsk There is currently a pull request open to add support for 0.10 here #282 |
Appreciate the 0.10 support. I see a consumer.properties file in conf/ where the security.protocol is defaulted to PlainText. Due to HIPAA constraints we are only allowed to only open SSL listeners on our brokers, but it doesn't appear that trying to assign the security.protocol=SSL and attempting to assign the Keystore (ssl.keystore.location) and TrustStore (ssl.truststore.location) can work. Actually, when I trace the properties back to KafkaStateActor.scala it appears to only be concerned with the ConsumerConfig and not the CommonConfig.SSLConfig. |
@benMain this is work in progress, we are in process off adding SSL to our clusters and then we'll update KM |
what version of SSL supports Kafka-Manager? How would you provide ssl.truststore information to KM? We can only use SSL on our Kafka cluster for security reasons. |
Great Tool. any timeline on supporting SASL_SSL? |
SSl part is really ambigous, i just succeed to get full information on full plaintext only |
Please add support for Kafka 0.10+
The text was updated successfully, but these errors were encountered: