akhq: Something wrong with my config file?

I’m trying to run with this config file - its the bare minimum from what i can see. The broker has sasl configured and its running on a remote machine ( URL specified in bootstrap ). Did I miss anything?

kafkahq:
  connections:
    Dev-multi-kafka-test:
      properties:
        bootstrap.servers: "kafka-node.workshop.works:9092"
            security.protocol: SASL_SSL
            sasl.mechanism: SCRAM-SHA-256
            sasl.jaas.config: org.apache.kafka.common.security.scram.ScramLoginModule required username="admin" password="123";
            ssl.truststore.location: /app/truststore.jks
            ssl.truststore.password: password
            ssl.keystore.location: /app/keystore.jks
            ssl.keystore.password: password
            ssl.key.password: password

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 18 (10 by maintainers)

Commits related to this issue

implemented sort on node logs, added generic sorting function (#141) — committed to tchiotludo/akhq by lyudmylatodoriko 4 years ago

Most upvoted comments

Only 1 machine is mandatory, give more is better but unneeded
Nothing is done to handle consul right now, you must specify direct connection with the broker.

for the docker run, it’s a normal behavior, you must use a -p 2000:8080, -p mean localPort:containerPort and you shoud access to webserver with localhost:2000 in your case

tchiotludo on Nov 14, 2019

The problem is that the option is changing how the cluster is defined and there is many case. Since it was a kafka configuration, I hope that the kafka docs will handle that case for me.

tchiotludo on Nov 25, 2019

Ok kafkahq is working, but the connection to kafka is down. You can go into the container with docker exec -it container-id bash and try connectivity with telnet or nc. Seems that your container can’t reach your ip

tchiotludo on Nov 14, 2019