Tools: Apache Kafka End of Life: Kafka Versions EOL Every 4 Months — Are You Behind? (2026)
Complete Kafka EOL Schedule
Why Kafka EOL Risk Is Different
The ZooKeeper Story: The Biggest Change in Kafka's History
How to migrate ZooKeeper → KRaft (without downtime)
Kafka Rolling Upgrade Guide
Step 1 — Control the protocol version
Step 2 — Upgrade one broker at a time
Step 3 — Update the protocol version
Step 4 — Check client compatibility
Check Your Full Data Stack Apache Kafka's release cadence is fast. A new minor version ships roughly every four months. EOL dates arrive quickly — and because Kafka sits at the heart of data pipelines, teams are slower to upgrade than they are with application-layer software. The result: a lot of production Kafka clusters running EOL versions handling compliance-critical data. Kafka 3.6 reached end of life in April 2026. If you're on 3.5 or earlier, you're already past EOL. The community maintains the two most recent minor versions. Everything else receives no further security patches or bug fixes. EOL Risk Score for Kafka 2.8: 84 Critical
View → endoflife.ai/score/apache-kafka/2.8 Kafka isn't stateless. It stores your data. An EOL web framework is a security risk. An EOL Kafka cluster is a security risk that also has custody of every message in your topics. CVEs affecting Kafka directly impact the confidentiality, integrity, and availability of your event streams. Historically significant Kafka CVEs include: In regulated industries — financial services, healthcare, any organization handling PII — an EOL Kafka cluster processing that data creates direct compliance exposure. Kafka 4.0, released March 2025, removed ZooKeeper support entirely. If your cluster still uses ZooKeeper for cluster metadata, you cannot upgrade to Kafka 4.0 without first migrating to KRaft. And ZooKeeper itself has its own EOL considerations: ZooKeeper 3.6 reached EOL March 2024. Kafka 3.7 and 3.8 support a live migration path: The migration runs while the cluster continues serving traffic. Once complete, the ZooKeeper ensemble can be decommissioned. Kafka supports rolling upgrades — upgrade brokers one at a time while the cluster continues serving traffic. During a rolling upgrade, pin inter.broker.protocol.version to the previous version: Only bump this after all brokers are on the new version. This allows mixed-version brokers to communicate safely during the upgrade window. Wait for the broker to rejoin and partition leadership to rebalance before proceeding to the next broker. After all brokers are upgraded: Rolling restart to apply. The Kafka protocol is backward-compatible, but broker upgrades may surface client-side issues. Update producers and consumers as part of the upgrade project, not after. Kafka doesn't run in isolation. Check EOL status for: Use the EOL Checker at endoflife.ai to look up any component's EOL status. Full article with EOL Risk Scores for every Kafka version: endoflife.ai/article-kafka-eol Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse
