Add 0.5.0 release announcement blog

Co-authored-by: Grace Grimwood <[email protected]>
Co-authored-by: Sam Barker <[email protected]>
Signed-off-by: Robert Young <[email protected]>

Author: 3 people

_posts/2024-03-13-release-0_5_0.md

@@ -0,0 +1,48 @@
+---
+layout: post
+title:  "Kroxylicious release 0.5.0"
+date:   2024-03-13 00:00:00 +0000
+author: "Robert Young"
+author_url: "https://www.github.com/robobario"
+categories:  [releases, kroxylicious, record-encryption]
+---
+
+The Kroxylicious project is very pleased to announce the release of [Kroxylicious 0.5.0](https://github.com/kroxylicious/kroxylicious/releases/tag/v0.5.0). See the [Changelog](https://github.com/kroxylicious/kroxylicious/blob/main/CHANGELOG.md#050) for a list of changes and summary of Deprecations, Changes and Removals.
+
+### 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 %}
+
+### Other Improvements
+
+* Support for Apache Kafka 3.7.0 API additions (Kroxylicious is version agnostic and can interface with all current broker and client versions, but must 
+be updated to intercept/forward new APIs or fields added to existing APIs of the Kafka Protocol)
+* A fix for upstream TLS connections failing, [@callaertanthony](https://github.com/callaertanthony)'s first PR contribution, thank you!
+* Added a `lowestTargetBrokerId` configuration for Port-per-broker Virtual Cluster exposition
+* Numerous bugfixes, documentation improvements, test enhancements
+
+### 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.