kfkit
Open-source tools for running Apache Kafka® in production.
Small, focused tools that lean on a Kafka cluster you already operate instead of asking you to run something new alongside it. A broker that is already the durable, ordered log at the centre of your system can answer more questions than it usually gets asked.
Projects
Distributed leases and leader election derived from a compacted topic, with a KEDA external scaler that keeps a workload running in one cluster at a time and fails it over when that cluster goes away. Brokers behind TLS, mTLS or SASL, Prometheus metrics, and an epoch to fence stale writers downstream. Go library, a container image and a Helm chart, signed and published on GHCR.
N replicas of any scalable target, a health gate that hands the lease on when the workload cannot run where it is held, several leases served by one scaler, and a standby mode that hands a cluster's lease over on purpose.
Who talks to what on a cluster: a drop-in replacement for the broker's
StandardAuthorizer that publishes JMX metrics per principal, client id,
topic, operation and request type. The first question it answers is who produces to
which topic; consumers and admins are counted the same way. The broker's verdict is
unchanged, idle series expire and a hard cap bounds their number. One jar for
Kafka 4.1 and later, with rules for the Prometheus JMX Exporter, signed on the
releases page and on Maven Central as dev.kfkit:kfkwho.
Role-based access control: an authorizer that adds roles and role bindings on top of the ACLs the broker already has. Roles only add access. A binding is an ACL record in the cluster's own metadata, so there is nothing else to run and the ACL tools you have keep working. The owner of a prefix hands out roles inside it, and nowhere else.
Seven roles, groups, a command that binds, lists and imports roles, and an extension
that applies the same bindings to Kafka Connect. One jar for Kafka 4.1 and later,
signed on the releases page and on Maven Central as dev.kfkit:kfkrbac.
Elsewhere
Everything lives on GitHub. Issues and pull requests are the place for questions — there is no mailing list and no chat.
kfkit is written and maintained by Ivan Abramov.