Skip to content

Commit fe95689

Browse files
committed
docs: Add warning about known issues for Kafka with KRaft
1 parent 36fe643 commit fe95689

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

modules/ROOT/partials/release-notes/release-25.11.adoc

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,20 @@ See https://github.com/stackabletech/demos/pull/289[demos#289].
7272

7373
===== Apache Kafka
7474

75-
This release adds experimental support for KRaft-managed Kafka clusters.
75+
[WARNING]
76+
====
77+
It should be noted, that there are multiple known issues including but not limited to:
78+
79+
* Automatic migration from Apache ZooKeeper to KRaft is not supported.
80+
* Scaling controller replicas might lead to unstable clusters.
81+
* Kerberos is currently not supported for KRaft in all versions.
82+
* Admin client access to controllers is not configured separately from the internal listeners.
83+
* Health monitoring is very basic.
84+
85+
See the xref:kafka:usage-guide/kraft-controller.adoc#_known_issues[known issues section] on the KRaft Controller page for an up-to-date list of known issues.
86+
====
87+
88+
This release adds experimental support for xref:kafka:usage-guide/kraft-controller.adoc[KRaft-managed] Kafka clusters.
7689
KRaft Controllers can be deployed instead of Apache ZooKeeper to manage the state of Kafka.
7790
KRaft is supported by all Kafka versions provided by SDP, and starting with Kafka 4 it is the only cluster management option available.
7891
See https://github.com/stackabletech/kafka-operator/pull/889[kafka-operator#889].

0 commit comments

Comments
 (0)