We’ve refreshed our dependencies, including an essential upgrade to Apache Kafka 4.2.0. We’ve also smoothed out the setup process, ensuring the new Kafka Queues feature works seamlessly straight out of the box.
Please let us know, through Slack or GitHub, if you find the extension interesting or helpful.
]]>The main change in this release is the upgrade of Testcontainers dependency from 1.x to 2.x. The Junit 5 Extension uses Testcontainers to create broker instances for your Junit tests (when you choose container-based provisioning). As a user of the Junit 5 Extension, the changes should be completely transparent to you.
Please let us know, through Slack or GitHub, if you find the extension interesting or helpful.
]]>The main highlights of this release are:
We’ve added a new Authorizer Filter that can authorize Topic operations using the same semantics as Kafka own Authorization API. This allows you to enforce authorizations rules at the proxy.
With this release, Record Encryption now has the capability to use Azure Vault for storage of the key material used to encrypt Kafka records.
Please let us know if you find the project interesting or helpful, and especially if you have deployed it in production. You can reach us through Slack, GitHub or even bsky).
]]>Please let us know, through Slack or GitHub, if you find the extension interesting or helpful.
]]>The main highlights of this release are:
This patch addresses an issue where the proxy failed to relay special handling logic introduced in Apache Kafka broker v4.0. This logic is required for deprecated ProduceRequest versions (v0-v2).
The bug prevented librdkafka clients older than v2.11.0 from enabling compression when connecting through the proxy. As librdkafka supports a wide variety of language bindings we are releasing this fix as a special patch release rather than waiting for v0.18.0.
Please let us know if you find the project interesting or helpful, and especially if you have deployed it in production. You can reach us through Slack, GitHub or even bsky).
]]>The main highlights of this release are:
io_uring a first class transport and an improved memory allocator.Get started with developing your own Custom Filter for Kroxylicious! You can now create a sample Filter project using a maven archetype to get up and running quickly. The generated project demonstrates how to structure a Filter project, and shows off our powerful integration testing tools which can simplify testing Filters against a real Apache Kafka cluster.
Run mvn archetype:generate -DarchetypeGroupId=io.kroxylicious -DarchetypeArtifactId=kroxylicious-filter-archetype -DarchetypeVersion=0.17.0
to get started!
For a more comprehensive guide to how to work with the Filter Archetype, see the Developer Quickstart.
We are currently discussing a proposal to release Kroxylicious 1.0.0, and formalize our support policy for patch releases. The aims are:
This will provide more predictability for everyone using Kroxylicious and developing against its APIs. Your feedback is essential to get this right. Please feel free to review and leave feedback on the proposal.
Please let us know if you find the project interesting or helpful, and especially if you have deployed it in production. You can reach us through Slack, GitHub or even bsky).
]]>The main highlights of this release are:
The main change in this release is Apache Kafka 4.1.0 compatibility. The proxy will now relay Kafka 4.1 specific versions of the Kafka RPC and your filters can intercept them.
Thanks to the work of hrishabhg, the proxy now sports connection count gauges, alllowing you to monitor downstream and upstream connection counts in realtime.
Please let us know, through Slack, GitHub or even bsky), if you find the project interesting or helpful and especially if you have deployed it in production.
]]>@SaslPlainAuth annotation and enables Users to customize the names of topics automatically created by the extension.
Support for earlier versions of Kafka is maintained, including versions that require Zookeeper. Just put the version of Kafka you want to use on the classpath - and everything else is automatic.
Please let us know, through Slack or GitHub, if you find the extension interesting or helpful.
]]>This is a critical feature release, fast-tracked to address a key resilience issue for our users.
Improved Bootstrap Resilience and Load Distribution:
Previously, when presented with a list of bootstrapServers, the proxy would only ever attempt to bootstrap connections using the first address in the list. This concentrated the bootstrapping load and created a single point of failure. See #1870.
To improve resilience, we have changed the default behaviour to round-robin over the supplied bootstrapServers each time the proxy receives a new connection from a client. This spreads the load and protects against an extended outage of the primary bootstrap address. For more control, you can now configure the selection strategy to be either round-robin or random. See the documentation for an example configuration.
Big thank you to The-East-Wind and opan for contributing towards the solution.
New Quickstart Guide: Record Encryption on Kubernetes: Looking for an encryption-at-rest solution for data stored in your Apache Kafka? We’ve got you covered!
This release includes a brand-new quickstart guide that will show you how to implement record encryption on Kubernetes from scratch, with no external dependencies. You’ll be encrypting in a snap!
Please let us know, through Slack, GitHub or even bsky), if you find the project interesting or helpful and especially if you have deployed it in production.
]]>New Authentication APIs for Plugin Authors: We are laying the groundwork for powerful client-identity-oriented Plugins. Our goal is to enable Plugins to access and influence client identity. This opens the door to advanced features like per-user authorization, message redaction, and much more!
This release takes the first major steps by adding APIs that allow Filters to:
New Back-Pressure Metrics: You can now pinpoint performance bottlenecks with new duration metrics that measure exactly how long the proxy is applying back-pressure to client connections.
Large Message Encryption Fix: See you later, alligator! We’ve squashed a critical bug in the Record Encryption Filter where encrypting events over 1MB would fail (#2504).
API Versions Negotiation Fix: We resolved a bug that prevented Redpanda Connect (using the franz-go client) from connecting when Kroxylicious was proxying older Kafka broker versions (#2450).
Please let us know, through Slack, GitHub or even bsky), if you find the project interesting or helpful and especially if you have deployed it in production.
]]>