Testing Kafka broker

This is a set of various configurations under which Kafka message broker can be run. Use them to spin up Kafka as a Docker container in a predefined configuration.

Configuration description

Each configuration is described in its own README file. Typical configuration includes:

• Kafka broker listening on port 909x (x is number between 1 and 9 and depends on the authentication setup which is run)
• Zookeeper listening on port 218x (x is number between 1 and 9 and depends on the authentication setup which is run)

About Zookeeper

Kafka and ZooKeeper work in conjunction to form a complete Kafka Cluster — with ZooKeeper providing the distributed clustering services, and Kafka handling the actual data streams and connectivity to clients.

At a detailed level, ZooKeeper handles the leadership election of Kafka brokers and manages service discovery as well as cluster topology so each broker knows when brokers have entered or exited the cluster, when a broker dies and who the preferred leader node is for a given topic/partition pair.

It also tracks when topics are created or deleted from the cluster and maintains a topic list. In general, ZooKeeper provides an in-sync view of the Kafka cluster.

Available configurations

• Kafka without any authentication
• Kafka with SASL_PLAIN authentication without TLS encryption
• Kafka with SASL_PLAIN authentication and TLS encryption
• Kafka with SASL_SCRAM authentication without TLS encryption
• Kafka with SASL_SCRAM authentication and TLS encryption