The Kroxylicious project is very pleased to announce the release of Kroxylicious 0.11.0. See the Changelog for a list of changes and summary of Deprecations, Changes and Removals.
The main change in this release is a revamped configuration file format. We hope this change means that Kroxylicious is more intuitive to configure. The changes are fully described in the changelog but to help you quickly update your configuration, compare the new and old configurations.
Backward compatibility has been maintained with the old format, so your old configuration will keep working for the next few releases. You’ll see deprecation warnings in the logs during startup.
We’ve added a new feature that lets you define Record Encryption’s behaviour when it cannot resolve a key encryption key (KEK) for a topic. You can now choose to have the Record Encrypton filter reject the producer batch so that the application will see errors, rather than letting the records through unencrypted. The default behaviour is unchanged.
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.