-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create 2024-09-13-junit-ext-and-kafka4.md (#75)
- Loading branch information
Showing
1 changed file
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
layout: post | ||
title: "Moving Kroxylicious Junit5 Extension to Kafka 4.0" | ||
date: 2024-09-13 00:00:00 +0000 | ||
author: "Keith Wall" | ||
author_url: "https://www.github.com/k-wall" | ||
categories: [junit5, kroxylicious, kafka4] | ||
--- | ||
|
||
Are you using the [kroxylicuous-junit5-extension](https://github.com/kroxylicious/kroxylicious-junit5-extension) to inject Kafka clusters into your integration tests? With Apache Kafka approaching the 4.0 milestone, we | ||
are looking for input to help decide the best way to manage the move to Kafka 4.0. | ||
|
||
Kafka 4.0 will will remove support for Zookeeper managed clusters. The Extension is currently capable of producing clusters managed by KRaft or Zookeeper, using | ||
whatever Kafka version you provide to it on the classpath. With Kafka 4.0's arrival the possibility of a Zookeeper managed cluster goes away. | ||
|
||
How important it is to you that the Extension continues to support the production of Kafka clusters managed by Zookeper when _Kafka 3.x_ is on the classpath? Talk to us on this issue [#389](https://github.com/kroxylicious/kroxylicious-junit5-extension/issues/389). |