technicaltalk/cp-kafka-cc repository overview

⁠cp-kafka-cc

confluentinc/cp-kafka:7.9.10 with LinkedIn Cruise Control⁠'s metrics reporter jar added, so Kafka brokers built from this image can publish the broker/partition metrics Cruise Control needs to monitor and rebalance a cluster.

⁠What's different from the base image

One file added on top of confluentinc/cp-kafka:7.9.10, nothing else changed:

/usr/share/java/kafka/cruise-control-metrics-reporter-2.5.146.jar

That path is on the broker's runtime classpath (confirmed by reading cp-kafka's own kafka-run-class script). The jar itself is not built here — it's copied from quay.io/strimzi/kafka:0.49.0-kafka-4.1.1, which bundles Cruise Control's own jars as part of the Strimzi project's Kafka image build.

⁠Dockerfile

FROM quay.io/strimzi/kafka:0.49.0-kafka-4.1.1 AS cc-libs

FROM confluentinc/cp-kafka:7.9.10
COPY --from=cc-libs /opt/kafka/libs/cruise-control-metrics-reporter-2.5.146.jar /usr/share/java/kafka/

⁠Usage

Set KAFKA_METRIC_REPORTERS=com.linkedin.kafka.cruisecontrol.metricsreporter.CruiseControlMetricsReporter (and the reporter's KAFKA_CRUISE_CONTROL_METRICS_TOPIC/KAFKA_CRUISE_CONTROL_METRICS_REPORTER_BOOTSTRAP_SERVERS env vars) the same way you'd configure any other cp-kafka broker — this image behaves identically to the stock one otherwise. Pair with Cruise Control running from quay.io/strimzi/kafka:0.49.0-kafka-4.1.1 directly (no build needed for that side) pointed at the same cluster.

⁠Tags

• 7.9.10-cc2.5.146 — cp-kafka 7.9.10 + cruise-control-metrics-reporter 2.5.146

⁠Verified

Booted as a real 3-node KRaft cluster (topic create/list/produce/consume all confirmed working), and confirmed the metrics reporter loads and auto-creates its Kafka topic (__CruiseControlMetrics) within seconds of broker startup.