This 105th edition of the Kafka Monthly Digest covers what happened in the Apache Kafka community in October 2026.
Releases
There are two new releases (4.4.0 and 4.3.2), and one release is in progress (4.5.0):
4.4.0
Omnia Ibrahim released Kafka 4.4.0 on October 22. You can find the announcement on the Apache Kafka blog. You can also check the release notes and the release plan in the wiki.
With 26 KIPs implemented this release brings several major new features and many improvements across all components.
Kafka brokers and clients
Updates to the Kafka broker and clients include the following:
Kafka Connect
Updates to Kafka Connect include the following:
- New configuration,
internal.topics.automatic.creation.enable, to specify whether Kafka Connect should automatically create its internal topics or not. (KIP-1209)
Kafka Streams
Updates to Kafka Streams include the following:
- Support for transactional state stores can be enabled using
enable.transactional.statestores. (KIP-892)
4.3.2
On October 23, Jiunn-Yang Huang released Kafka 4.3.2. This bug fix release fixes 59 issues. You can find the announcement on the blog and the release plan in the wiki.
4.5.0
The next milestone for Kafka 4.5.0 is KIP freeze on January 13 2027. You can find the release plan in the wiki.
Kafka Improvement Proposals
Last month, the community submitted 11 KIPs (KIP-1379 to KIP-1390, KIP-1380 was skipped). I'll highlight a few of them:
- KIP-1381: Allow Brokers to Disable Compression Types for Client Writes: Kafka supports multiple compression algorithms using third-party libraries and all of them apart from gzip include native code. Security issues in native code can be critical and Kafka depends on the community of each library to address issues in a timely manner. As an attempt to mitigate this risk, this KIP proposes enabling cluster administrators to specify which compression algorithms to enable.
- KIP-1383: Standard record headers for content type: This KIP proposes introducing standard headers to describe the record key and value types. It would include default content types such as int, long, string, etc, and also allow custom types via a MIME special value.
- KIP-1389: Surface effective group configurations to clients: When using the new group protocol, via consumer, share consumer or Streams, several group configurations are computed by the coordinator and may override values configured on the clients. At the moment, not all the configurations are exposed back to the clients and this can make troubleshooting issues harder. This KIP aims at providing a mechanism to expose all the group configurations that are effectively used by the coordinator when handling a group.
Community Releases
I selected releases of some open source community projects:
- strimzi-kafka-operator 1.3.0: Strimzi is a Kubernetes Operator for running Kafka. This release adds support for Kafka 4.2.2. It also introduces 2 new features in early access, an integration with cert-manager for issuing certificates, and a mechanism to configure internal cluster security (authentication and authorization).
- Cruise Control 3.1.0: Cruise Control is a tool to dynamically rebalance workloads and self-heal Kafka clusters. The project has been donated by LinkedIn to the Linux Foundation. This is the first release since the donation and it mostly focuses on updating dependencies, including Kafka to 4.3.1, to address CVEs.
- Kroxylicious 0.25: Kroxylicious is an open source pluggable framework for writing network proxies that understand the Apache Kafka protocol. It adds Kubernetes-based authentication for HashiCorp Vault support and improves Kubernetes load balancer service integration.
Blogs
I selected some interesting blog articles that were published last month: