Skip to content

Commit fb76e46

Browse files
authored
Release notes for 0.11.0 (#107)
Signed-off-by: Keith Wall <[email protected]>
1 parent db3471f commit fb76e46

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

_posts/2025-03-17-release-0_11_0.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
layout: post
3+
title: "Kroxylicious release 0.11.0"
4+
date: 2025-03-17 00:00:00 +0000
5+
author: "Keith Wall"
6+
author_url: "https://github.com/k-wall"
7+
# noinspection YAMLSchemaValidation
8+
categories: blog kroxylicious releases
9+
tags: [ "releases", "kroxylicious" ]
10+
---
11+
12+
The Kroxylicious project is very pleased to announce the release of [Kroxylicious 0.11.0](https://github.com/kroxylicious/kroxylicious/releases/tag/v0.11.0). See the [Changelog](https://github.com/kroxylicious/kroxylicious/blob/main/CHANGELOG.md#0110) for a list of changes and summary of Deprecations, Changes and Removals.
13+
14+
### Revamped configuration file format
15+
16+
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](https://github.com/kroxylicious/kroxylicious/blob/main/CHANGELOG.md#0110) but
17+
to help you quickly update your configuration, compare the [new](https://raw.githubusercontent.com/kroxylicious/kroxylicious/refs/tags/v0.11.0/kroxylicious-app/example-proxy-config.yaml) and [old](https://raw.githubusercontent.com/kroxylicious/kroxylicious/refs/tags/v0.10.0/kroxylicious-app/example-proxy-config.yaml) configurations.
18+
19+
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.
20+
21+
### New policy to control record encryption's behaviour when a KEK doesn't resolve
22+
23+
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,
24+
rather than letting the records through unencrypted. The default behaviour is unchanged.
25+
26+
### Feedback
27+
28+
Please let us know, through [Slack](https://kroxylicious.slack.com), [GitHub](https://github.com/kroxylicious/kroxylicious/issues) or even [bsky](https://bsky.app/profile/kroxylicious.io)), if you find the project interesting or helpful and especially if you have deployed it in production.

0 commit comments

Comments
 (0)