Release announcement for 0.5.1

rh-pre-commit.version: 2.0.1
rh-pre-commit.check-secrets: ENABLED

Author: SamBarker

_posts/2024-04-10-release-0_5_1.md

@@ -0,0 +1,48 @@
+---
+layout: post
+title:  "Kroxylicious release 0.5.1"
+date:   2024-04-10 00:00:00 +0000
+author: "Sam Barker"
+author_url: "https://www.github.com/sambarker"
+categories:  [releases, kroxylicious, record-encryption]
+---
+
+The Kroxylicious project is very pleased to announce the release of [Kroxylicious 0.5.1](https://github.com/kroxylicious/kroxylicious/releases/tag/v0.5.1). See the [Changelog](https://github.com/kroxylicious/kroxylicious/blob/main/CHANGELOG.md#051) for a list of changes and summary of Deprecations, Changes and Removals.
+
+### Fixes and Improvements in 0.5.1
+
+* [@luozhenyu](https://github.com/luozhenyu) noticed that we didn't support Kafka 0.10.0 properly and provided a fix [PR#1110](https://github.com/kroxylicious/kroxylicious/pull/1110) so that our handling is inline with that of official [java client](https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/requests/ApiVersionsResponse.java#L90-L106)
+* [@luozhenyu](https://github.com/luozhenyu) also spotted that we were not cancelling the timeouts when filters sent additional requests to the broker.
+* The proxy now fails to start if any of the required cipher suites are unavailable.
+
+
+### Record Encryption
+
+This release was focused on refining [Record Encryption](/use-cases/#encryption-at-rest) to be ready for experimentation in secure environments, adding:
+* Enable users to configure Hashicorp Vault TLS, providing custom keystore and truststore
+* Enable users to supply the Hashicorp Vault token via file rather than having to inject it into the proxy configuration
+* Include Record Encryption filter (and other Kroxylicious project supported filters) in the binary distribution
+* Release a Docker image `quay.io/kroxylicious/kroxylicious` also containing the supported filters
+* Improvements in how we manage and control the usage of key material, preparing to support alternate Ciphers and configurable Additional Authenticated Data
+
+The protocol for immutable encrypted data written to the broker is now aligned with our initial design. We guarantee data encrypted with version 0.5.0 
+of the Filter will be decryptable by all future versions of the Record Encryption Filter forever (assuming the keys stored in the KMS remain available for decryption).
+
+{% capture record_encryption_note %}
+Until now we have used the term Envelope Encryption when describing the Filter. Going forward we will use the name Record Encryption 
+to better describe the granularity that encryption is happening at. Encryption is done per [record](https://kafka.apache.org/documentation/#record).
+Envelope Encryption is how we encrypt those records. Record Encryption is how we implement Encryption-At-Rest.
+{% endcapture %}
+{% include bs-alert.html type="primary" icon="info-circle-fill" content=record_encryption_note %}
+
+### Artefacts
+
+You'll find binaries attached to the GitHub [release](https://github.com/kroxylicious/kroxylicious/releases/tag/v0.5.0), and available through [Maven Central](https://repo1.maven.org/maven2/io/kroxylicious/kroxylicious-app/0.5.0/).
+
+Docker images are hosted at [quay.io/kroxylicious/kroxylicious](https://quay.io/repository/kroxylicious/kroxylicious)
+
+### Feedback
+
+We are eager for any feedback, you can create an [issue in GitHub](https://github.com/kroxylicious/kroxylicious/issues) if you have any problems or want a
+feature added.
+``