Messaging

Apache Kafka Releases

Track Apache Kafka releases, KRaft migration timeline (ZooKeeper removal), version feature comparison, client compatibility matrix, and upgrade complexity guidance.

Official Site Documentation

—

Total Versions

—

Supported

—

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

3.3

3.5

3.6

3.7

3.8

3.9

4.0

2022 2023 2024 2025 2026 2027 2028

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active / LTS

Maintenance

Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

3.5/3.6 (ZooKeeper) 3.8+ (KRaft) High Difficulty

Est. 4-8 hours for the upgrade + 4-8 hours for KRaft migration

Breaking Changes

ZooKeeper deprecated (3.5) and migration required before 4.0
KRaft controller nodes must be provisioned
Metadata migration from ZooKeeper to KRaft
Some ZooKeeper-specific configurations removed
Inter-broker protocol version must be stepped through each version
ACL storage moved from ZooKeeper to KRaft

Migration Notes

The ZooKeeper to KRaft migration is the most significant Kafka upgrade ever. Steps: 1) Upgrade to 3.7+ (minimum for migration tooling), 2) Add KRaft controller nodes, 3) Run kafka-metadata.sh to migrate metadata, 4) Switch brokers to KRaft mode, 5) Decommission ZooKeeper. Plan 1-2 days for a production cluster. Test thoroughly in staging.

3.8/3.9 (KRaft) 4.0 Medium Difficulty

Est. 2-4 hours (if already on KRaft)

Breaking Changes

ZooKeeper support completely removed
Must be on KRaft before upgrading
Deprecated broker configurations removed
Client protocol minimum version bumped
Some internal topic format changes

Migration Notes

If you are already on KRaft, the 4.0 upgrade is a standard rolling upgrade. If you are still on ZooKeeper, you MUST migrate to KRaft on 3.8/3.9 first. The 4.0 binary will not start with ZooKeeper configuration. Update inter-broker protocol version after all brokers are upgraded.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version	EOL Risk	CVE Risk	Ecosystem	Cloud Support	Overall	Recommended Action
Apache Kafka 3.5 and older	Critical	High	Unsupported	Degrading	Critical	No patches — ZooKeeper deprecation deadline approaching
Apache Kafka 3.6/3.7	High	Medium	Maintenance	Full	High	Migrate to KRaft and upgrade to 3.9+
Apache Kafka 3.8	Medium	Low	Supported	Full	Medium	Supported — start KRaft migration
Apache Kafka 3.9	Low	Low	Active	Full	Low	Current — recommended for KRaft migration
Apache Kafka 4.0	None	Low	Active	Full	Low	Latest — KRaft-only, fully modern

Kafka supports the latest 2-3 minor versions. ZooKeeper removal in 4.0 creates urgency for KRaft migration. Assessed March 2026.

Apache Kafka Version Feature Comparison

Side-by-side feature differences across major versions.

Feature	3.5	3.7	3.8	3.9	4.0
ZooKeeper support	Deprecated	Deprecated	Deprecated	Deprecated	Removed
KRaft (Kafka Raft)	Stable	Stable	Stable	Enhanced	Required
Tiered storage	Alpha	Beta	Stable	Enhanced	Enhanced
Client quotas	Stable	Enhanced	Enhanced	Enhanced	Enhanced
Transactions	Stable	Stable	Enhanced	Enhanced	Enhanced
JBOD storage support	Legacy	KRaft	KRaft	KRaft	KRaft
Consumer group protocol	Classic	Classic	New (opt-in)	New (opt-in)	New (default)
Java minimum	11	11	17	17	17
Migration tooling	Basic	Improved	Stable	Enhanced	N/A (no ZK)

Embed Badges

Add live Apache Kafka status badges to your README, docs, or dashboard.

Health Status

Overall support health

![Apache Kafka Health Status](https://img.releaserun.com/badge/health/apache-kafka.svg)

EOL Countdown

Next end-of-life date

![Apache Kafka EOL Countdown](https://img.releaserun.com/badge/eol/apache-kafka.svg)

Latest Version

Current stable release

![Apache Kafka Latest Version](https://img.releaserun.com/badge/v/apache-kafka.svg)

CVE Status

Known vulnerabilities

![Apache Kafka CVE Status](https://img.releaserun.com/badge/cve/apache-kafka.svg)

Frequently Asked Questions

Common questions about Apache Kafka releases and lifecycle.

What is the KRaft migration and when should I do it?

KRaft (Kafka Raft) replaces ZooKeeper for cluster metadata management. ZooKeeper support was deprecated in Kafka 3.5 and removed in Kafka 4.0. If you are on Kafka 3.x, you must migrate to KRaft before upgrading to 4.0. The migration is online (no downtime): enable KRaft controllers alongside ZooKeeper, migrate metadata, then decommission ZooKeeper. Do this now if you are on 3.6+.

How does Kafka versioning work?

Kafka follows semantic versioning. Minor releases (3.6, 3.7, 3.8) come roughly every 4 months and may include new features. Patch releases fix bugs and security issues. The project maintains the latest 2-3 minor versions with patches. Major versions (3.0, 4.0) introduce breaking changes. Kafka 4.0 is the biggest breaking change in years (ZooKeeper removal).

How do I upgrade Kafka safely?

Kafka supports rolling upgrades with zero downtime. Upgrade brokers one at a time: stop the broker, upgrade the binary, start it, wait for ISR (in-sync replica) recovery, then move to the next broker. The critical step is the inter-broker protocol version: set it to the OLD version first, upgrade all brokers, then bump the protocol version in a second rolling restart. Never skip major versions.

What is the Kafka client compatibility matrix?

Kafka clients are backward and forward compatible within limits. A client with protocol version N can talk to brokers running version N-2 to N+2 (approximately). However, new features require matching client and broker versions. The Java client is always the first to support new features. Third-party clients (librdkafka, confluent-kafka-python, sarama) may lag. Pin your client version and test against your broker version.

Should I use Apache Kafka or Confluent Platform?

Apache Kafka is the open-source core. Confluent Platform adds Schema Registry, ksqlDB, Connect Hub, Confluent Control Center, and enterprise features (multi-region replication, RBAC, audit logs). Confluent Cloud is a fully managed SaaS. For most teams, Apache Kafka + Schema Registry (available separately) is sufficient. Confluent Platform is for teams needing stream processing (ksqlDB) or enterprise compliance features.

What are Kafka alternatives I should consider?

Redpanda is a C++ Kafka-compatible engine that runs without ZooKeeper or JVM, offering lower latency and simpler operations. Apache Pulsar offers multi-tenancy, geo-replication, and tiered storage natively. NATS JetStream is simpler for lightweight messaging. RabbitMQ Streams adds streaming on top of RabbitMQ. For high-throughput event streaming at scale, Kafka or Redpanda. For simpler messaging, NATS or RabbitMQ.

Related Tools

Dep EOL Scanner

Check your dependencies for end-of-life packages.

Stack Health Scorecard

Get an overall health grade for your tech stack.

Release Index

Browse all tracked platforms and their release timelines.

Browse All Version History