Understanding Connectivity Issues
Conduktor is not (yet) magical: Apache Kafka limitations
If you know you cannot connect from your local computer to your Apache Kafka cluster using the Kafka CLI, this means that Conduktor will also not be able to connect. To test your connectivity to Kafka, you can run the following command:- your Apache Kafka
advertised.listeners
are configured using internal IPs/DNS that your computer cannot resolve - you’re using Docker and you did not expose the Kafka ports to your host, where Conduktor is running
- your computer cannot resolve the IPs/DNS exposed by Apache Kafka because your cluster is running in a private subnet not known to your computer
Just remember that Conduktor is running on your machine, running on your network, which may be different from the network your Apache Kafka clusters are running.
Understanding Kafka Listeners
Part of understanding why your CLI (and therefore Conduktor) can’t connect to your Kafka Cluster is due to your knowledge of how the Apache Kafka listeners work. As such, we heavily recommend for you to read this blog to learn about Kafka listeners.Another longer blog can be found at: https://www.confluent.io/blog/kafka-client-cannot-connect-to-broker-on-aws-on-docker-etc/
.png?fit=max&auto=format&n=5TjI4-HLqdnQIYNU&q=85&s=d59ca16aba1dfead2ae0afc5462e7eca)
Connecting to Kafka behind a bastion / SSH hops
Connecting to Apache Kafka through a simple SSH tunnel with Conduktor is impossible, due to how the Apache Kafka protocol works. No client can currently do this setup:.png?fit=max&auto=format&n=5TjI4-HLqdnQIYNU&q=85&s=ac87cb3844a5f6d4446838800c40deed)
Connecting to Kafka in a private cloud
This setup does not work, because your computer will not be able to resolve the private subnet IP/DNS exposed by Apache Kafka:%20(1).png?fit=max&auto=format&n=TnAtm2P5ki9OGejC&q=85&s=e6803d0e336f1e506077866902551b07)
.png?fit=max&auto=format&n=5TjI4-HLqdnQIYNU&q=85&s=12e60c3a96829fc15e1cb28450136afc)