The CloudKarafka team proudly presents the Kafka REST Proxy integration.The Kafka REST Proxy gives you the opportunity to receive metadata from a cluster and produce and consume messages over a simple REST API. This feature can easily be enabled from the Control Panel for your cluster.
If you have an application that doesn’t support the Kafka-client, or missing a script that read the state of the cluster to see that everything looks good - Kafka REST Proxy could be a perfect alternative.
The REST Proxy is always enabled on all of the nodes in your cluster, they all use the same consumer group so even if you request data from different nodes you won’t get duplicates. You can access the REST proxy by using the hostname for a specific node, or better yet, use the hostname for the cluster and the load balancer will distribute the calls for all nodes.
The REST Proxy can be accessed without authentication for instances running on Amazon Web Services or Google Cloud, where we can peer the VPC where Kafka runs with your VPC. Within the peered VPC you can access the rest proxy using the private IP and the default port 8082, which you can find in the Control Panel.
As a customer, you need authentication for the ability to use REST Proxy from outside of the VPC. Presets have been made so that you can reach the REST Proxy over TLS and use Basic auth. Further information about the integration setup can be found on the same page as you enable the REST Proxy.
The REST Proxy works great together with Schema Registry, all you have to do is make sure the Schema Registry is started before you start the REST Proxy. The REST Proxy will find the Schema Registry automatically and you can without any configuring start producing and consuming messages using the AVRO data format.
Feel free to send us any feedback you might have at firstname.lastname@example.org