Back to blog

OSSeva Blog

Operations

Kafka 3.8 End of Support Checklist: 12 Steps Before 2 December 2026

9 min read

The short answer

Confluent Platform 7.8, which ships Apache Kafka 3.8, reaches end of support on 2 December 2026 for community and standard support, and a year later for Platinum. Apache's last 3.8 release, 3.8.1, came out on 29 October 2024. To prepare: find every 3.8 broker, work out which date applies to you, choose a target, rehearse the upgrade and decide cover for anything that cannot move.

The date in this checklist belongs to Confluent, not to the Apache project. If you run Apache Kafka 3.8 directly, you are already past the last 3.8 release, and 2 December 2026 is a deadline only if Confluent supports your cluster. The steps are the same either way.

Running Apache Kafka in production? OSSeva patches and supports it, end-of-life versions included.

Apache Kafka extended support: what is covered

Which end dates apply to Kafka 3.8?

DistributionWhat the vendor saysDate
Apache KafkaLast 3.8 release is 3.8.1. Apache's downloads page lists no end date for any line.3.8.1 released 29 Oct 2024
Confluent Platform 7.8.x (Kafka 3.8.x), Community and Standard supportEnd of support2 Dec 2026
Confluent Platform 7.8.x, Platinum supportEnd of support, one year later2 Dec 2027

Sources: Confluent's Platform and Apache Kafka compatibility table and Apache's downloads page, both checked 11 November 2026. Confluent says standard support is any support level below Platinum, and that the end of support date covers every maintenance release of the minor version. OSSeva's Kafka 3.8 end-of-life page counts 3.8 as past community end of life from 6 November 2024, the day 3.9.0 shipped. Running Kafka on Amazon MSK is a different calendar; see MSK Kafka version end of support.

Phase 1: Find and inspect

Step 1. List every Kafka 3.8 broker and say which distribution it is

Run these on each host and in each image registry, then look for the clusters nobody lists.

ls libs/ | grep -E "^kafka_"                          # Apache install: the jar name carries the version
rpm -qa | grep -i -E "confluent|kafka"                 # RPM hosts
dpkg -l | grep -i -E "confluent|kafka"                 # Debian and Ubuntu hosts
grep -rnE "apache/kafka:3\.8|cp-(kafka|server):7\.8" --include="*.yml" --include="*.yaml" --include="Dockerfile*" .
kubectl get pods -A -o custom-columns=NS:.metadata.namespace,POD:.metadata.name,IMAGE:.spec.containers[*].image | grep -E "kafka:3\.8|cp-(kafka|server):7\.8"

Count the copies as well: test and staging clusters, MirrorMaker or replication targets, single-broker development clusters that grew into something real, and Kafka bundled inside vendor products you do not control. Note for each one whether the image or package is Apache 3.8.x or Confluent Platform 7.8.x, because the support date differs.

Step 2. Decide which date applies to each cluster

Use the table above. Apache 3.8 has no further Apache releases. Confluent Platform 7.8 has support until 2 December 2026, or 2 December 2027 with Platinum. A cluster someone else operates for you has the provider's own date, so ask for it in writing.

Step 3. Record the mode and the metadata version

Kafka 4.0 and later run in KRaft mode only. A cluster still on ZooKeeper cannot go straight to 4.x.

grep -E "^(process\.roles|zookeeper\.connect|node\.id|broker\.id)" config/server.properties config/kraft/*.properties
bin/kafka-features.sh --bootstrap-server localhost:9092 describe

A server with process.roles set is in KRaft mode, and a server with zookeeper.connect and no process.roles is on ZooKeeper. The describe output shows the finalized metadata version, which is the number the upgrade steps later raise.

Step 4. Inventory clients, connectors and Streams applications

Apache's upgrade notes say clients, including Kafka Streams and Connect, must be on version 2.1 or higher before they move to 4.0, and that many deprecated client APIs and old protocol versions were removed in 4.0. List the client library version for every producer, consumer and Streams application, every Connect worker and connector, and every third-party tool that connects. Clients on 4.0 and later need Java 11, and brokers, Connect and tools need Java 17. Record the Java version for each. The compatibility details are in Kafka 4.0 client compatibility (KIP-896).

Step 5. Inventory everything that talks to ZooKeeper

Monitoring agents, admin scripts, lag exporters, older consoles and any custom tooling that reads broker metadata from ZooKeeper stop working when the cluster moves to KRaft. Find them before the migration, not after. The ZooKeeper side of the move is in ZooKeeper to KRaft migration.

Phase 2: Choose the path

Step 6. Pick the target and the route

You runRoute
3.8 in KRaft modeApache's notes list an upgrade to 4.x from any version 3.3.x or later in KRaft mode. No bridge release is needed. Upgrade brokers one at a time, then finalize the metadata version.
3.8 on ZooKeeperMigrate to KRaft first. Apache says the last bridge release is 3.9, so upgrade to 3.9 (latest is 3.9.2), migrate to KRaft, then upgrade to 4.x. See Kafka 3 to 4 upgrade.

Apache's latest releases on its downloads page are 4.4.0 (22 October 2026) and 4.3.2 (23 October 2026). Apache lists no end date for 4.x lines, so choose the target by what you must run and by the vendor dates below if you use Confluent.

Step 7. If you run Confluent Platform, choose the platform version by its dates

Confluent PlatformKafkaCommunity endsStandard endsPlatinum ends
7.8.x3.8.x2 Dec 20262 Dec 20262 Dec 2027
7.9.x3.9.x19 Feb 202719 Feb 202719 Feb 2028
8.0.x4.0.x11 Jun 202611 Jun 202711 Jun 2028
8.1.x4.1.x15 Oct 202615 Oct 202715 Oct 2028
8.2.x4.2.x4 Mar 20274 Mar 20284 Mar 2029
8.3.x4.3.x17 Jun 202717 Jun 202817 Jun 2029
8.4.x4.4.x27 Oct 202727 Oct 202827 Oct 2029

Source: Confluent's Platform and Apache Kafka compatibility table, checked 11 November 2026. Confluent says that, from Platform 8.0, Community support follows the Kafka release cycle more closely. 7.9 is the last line on Kafka 3.9, and it ends only 11 weeks after 7.8 for Community and Standard, so moving 7.8 to 7.9 buys little time.

Phase 3: Rehearse and protect

Step 8. Capture configuration, offsets and the rollback limits

Export topic configuration, ACLs, quotas, and consumer group offsets for the groups that matter.

bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --describe --group my-group

Then read the rollback limits before the change window. Apache's notes say cluster metadata downgrade is not supported when the versions in between have metadata changes, and Kafka 4.0 has them. For a ZooKeeper to KRaft migration, the steps and their rollback notes are in the 3.9 documentation that Apache points to. Write down, per cluster, the last point at which you can still go back.

Step 9. Rehearse on a production-shaped copy

  1. Build a test cluster with the same broker count, topic layout, client mix and security settings.
  2. Run the full upgrade, including the metadata version finalization, and time each step.
  3. Run real producers, consumers, Streams applications and Connect jobs against it, and compare latency and consumer lag with the 3.8 baseline.
  4. For ZooKeeper clusters, rehearse the KRaft migration separately, then the 4.x upgrade.

Phase 4: Cut over

Step 10. Upgrade in order and finalize last

Apache's rolling upgrade is one broker at a time: shut the broker down, update the code, restart it, and confirm the cluster behaves before the next. Finalize the metadata version only after the whole cluster has run on the new version for long enough to be sure.

bin/kafka-features.sh --bootstrap-server localhost:9092 upgrade --release-version 4.0

Use the release version of your target. Upgrade clients on their own schedule, but not before the brokers they talk to, and not from a version older than 2.1 to 4.0.

Step 11. Verify and clean up

Re-run the step 1 commands and expect no 3.8 results. Check consumer lag, under-replicated partitions, controller health and error rates through a full business cycle. Keep the old binaries or images until the rollback window you wrote in step 8 has closed, then remove them and update the inventory and end-of-life register.

Phase 5: Plan for what cannot move

Step 12. Choose a cover option and record it

Some clusters will not move by 2 December: a vendor application certified only on 3.8, a connector with no 4.x build, a ZooKeeper migration still being rehearsed, or a change freeze. For each, write down the owner, the target date, compensating controls and who accepted the risk.

What changes on 2 December 2026

ItemOn the day
Your Kafka 3.8 brokersKeep running. Nothing is switched off.
Apache releases for 3.8No change. The last was 3.8.1 in October 2024.
Confluent Platform 7.8 Community and Standard supportEnds. Platinum support continues to 2 Dec 2027.
Self-managed clusters with no other coverNo supplier fixes. Scanners that check lifecycles will flag the version.

One-page printable checklist

DoneStepOwnerEvidence
☐1. Every 3.8 broker listed, with its distributionInventory sheet
☐2. End date decided per clusterDate and source per cluster
☐3. Mode (ZooKeeper or KRaft) and metadata version recordedfeatures describe output
☐4. Clients, connectors and Streams apps listed with versions and JavaClient matrix
☐5. ZooKeeper-dependent tooling foundTooling list
☐6. Target and route chosen per clusterDecision note
☐7. Confluent Platform target chosen by its dates (if used)Version and date
☐8. Configuration and offsets captured, rollback limits writtenRunbook
☐9. Rehearsal run and timed on a production-shaped copyTest log
☐10. Upgrade done in order, metadata finalized lastChange ticket
☐11. Verification done and old 3.8 removedClean inventory
☐12. Cover recorded for every cluster left on 3.8Signed exception record

Frequently asked questions

When does Kafka 3.8 reach end of support?

For Confluent Platform 7.8, which ships Kafka 3.8, Community and Standard support end on 2 December 2026 and Platinum on 2 December 2027. Apache published its last 3.8 release, 3.8.1, on 29 October 2024 and lists no end date for 3.8.

Will Kafka 3.8 stop working on 2 December 2026?

No. Brokers keep running. What ends is Confluent's support for Platform 7.8 at the Community and Standard levels, and nothing changes in Apache's release stream, which stopped at 3.8.1.

Can I upgrade Kafka 3.8 straight to 4.x?

If the cluster is in KRaft mode, Apache's notes list an upgrade to 4.x from any version 3.3.x or later. If it is on ZooKeeper, no: Kafka 4.0 removed ZooKeeper mode, the last bridge release is 3.9, and the cluster must be migrated to KRaft first.

What Java version does Kafka 4 need?

Brokers, Connect and tools need Java 17. Clients and Kafka Streams applications need Java 11. Both come from Apache's 4.0 upgrade notes.

Is Confluent Platform 7.8 the same as Apache Kafka 3.8?

No. Confluent Platform 7.8 is Confluent's distribution, which ships Apache Kafka 3.8.x with Confluent components. Its support dates come from Confluent, and Apache has its own release history. See Apache Kafka vs Confluent.

How can I keep Kafka 3.8 patched on my own servers?

Use a third-party patched build. OSSeva patches Apache Kafka 3.8.x, with Critical CVEs within 48 hours and High within 7 days, and supports the Apache distribution rather than a fork. See Kafka 3.x on ZooKeeper: stay supported, then move to KRaft.

Tags

Apache KafkaKafka 3.8End of SupportChecklistKRaftUpgrade

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call