Supported Versions and Interoperability for Confluent Platform

This topic provides the supported version and interoperability information for Confluent Platform and its components for Confluent Platform 8.0 and older. Note that older versions are removed as their support windows end. If a newer Confluent Platform version exists, you can select it in the version picker in the lower left to view its interoperability and version support.

Ready to build?

Sign up for Confluent Cloud with your cloud marketplace account and unlock $1000 in free credits: AWS Marketplace, Google Cloud Marketplace, or Microsoft Azure Marketplace.

Confluent Platform and Apache Kafka compatibility

The following table lists Kafka and Confluent Platform compatibility.

Important

Change Notice: Effective with Confluent Platform 8.0, Confluent Platform, Community version transitioned to follow the Kafka release cycle more closely. The Kafka community provides about one year of patch support for a Kafka version, from the minor version release date, and Confluent Community software follows a similar support schedule. Confluent customers using a Confluent Enterprise license will continue to receive patch updates for up to three years following minor version release.

Confluent Platform Apache Kafka® Release Date Confluent Community software End of Support Confluent Enterprise Standard End of Support Confluent Enterprise Platinum End of Support
8.0.x 4.0.x June 11, 2025 June 11, 2026 June 11, 2027 June 11, 2028
7.9.x 3.9.x February 19, 2025 February 19, 2027 February 19, 2027 February 19, 2028
7.8.x 3.8.x December 2, 2024 December 2, 2026 December 2, 2026 December 2, 2027
7.7.x 3.7.x July 26, 2024 July 26, 2026 July 26, 2026 July 26, 2027
7.6.x 3.6.x February 9, 2024 February 9, 2026 February 9, 2026 February 9, 2027
7.5.x 3.5.x August 25, 2023 August 25, 2025 August 25, 2025 August 25, 2026
7.4.x 3.4.x May 3, 2023 May 3, 2025 May 3, 2025 May 3, 2026
7.3.x 3.3.x November 4, 2022 November 4, 2024 November 4, 2024 November 4, 2025
7.2.x 3.2.x July 6, 2022 July 6, 2024 July 6, 2024 July 6, 2025

Note the following about Confluent Platform versions and support levels:

  • Standard support means any support level below Platinum support. For example, if you have Gold support, you have Standard support. The two year support policy is standard for commerical components. End of support is extended one year for Platinum support agreements.

  • The end of support date applies to minor versions and any maintenance versions that come after the minor version. This means that maintenance versions follow the same two year lifecycle of the minor version. For example, standard support for Confluent Platform 7.4.x ends on May 3, 2025.

  • Platinum tier support is not offered for Confluent for Kubernetes (CFK).

    Starting with CFK 2.9, the standard support policy of CFK is for 2 years from the first patch release (.0) date.

    You can apply your Confluent Platform Platinum tier support contract to the Confluent Platform components deployed by CFK when both of the following conditions are true:

    • You are on a currently supported version of CFK.
    • The Confluent Platform version you want to use is compatible with a currently supported version of CFK.

    For the CFK-specific support policy and supportability between CFK and Confluent Platform versions, see Supported versions of Confluent Platform and CFK.

  • Each version of Confluent Platform includes several component services which are only compatible in that specific Confluent Platform version. There are exceptions, including clients and Confluent Control Center, which can be used across versions. All services included in Confluent Platform are supported by Confluent.

Preview releases

Preview features are not “Supported Software” under Confluent’s support policies and features designated with “preview” status in this documentation are not intended for production use. Preview features should only be used for evaluation and non-production testing purposes or to provide feedback to Confluent.

Confluent encourages customers to submit questions and suggestions about preview features using the Confluent Support Portal.

Additionally, Confluent may make changes to preview user experience and APIs before they are released for production use.

Operating systems

Confluent Platform and clients support these operating systems.

It is recommended that you run Confluent Platform across uniform OS, Confluent Platform, and Java versions.

Confluent Platform supports both X86 and ARM64 hardware architecture. ARM64 is supported in Confluent Platform 7.6.0 and later. For more information on required hardware, see Hardware.

Operating System Linux Kernel 8.0.x 7.9.x 7.8.x 7.7.x 7.6.x 7.5.x 7.4.x 7.3.x 7.2.x
AlmaLinux 9 5.14 yes yes yes no no no no no no
AlmaLinux 8 4.18 yes yes yes no no no no no no
Amazon Linux 2023 6.1 yes yes yes yes no no no no no
Debian 12 (bookworm) 6.1 yes yes yes yes no no no no no
Debian 10 (buster) [1] 4.19 no no no yes yes yes yes yes yes
RHEL 9.x 5.14 yes yes yes yes yes yes yes no no
RHEL/CentOS 8.x 4.18 yes yes yes yes yes yes yes yes yes
RHEL/CentOS 7.x [3] 3.10 no no no no yes yes yes yes yes
Rocky Linux 9 5.14 yes yes yes yes yes no no no no
Rocky Linux 8 4.18 yes yes yes yes yes no no no no
Ubuntu 24.04 LTS (noble) [2] 6.8 yes yes no no no no no no no
Ubuntu 22.04 LTS (jammy) [2] 5.15 yes yes yes no no no no no no
Ubuntu 20.04 LTS (focal) 5.4 yes yes yes yes yes yes yes yes yes
Ubuntu 18.04 LTS (bionic) [1] 4.15 no no no yes yes yes yes yes yes

Footnotes

[1](1, 2) Support for these operating systems has been removed in Confluent Platform 7.8.x because they have reached their end of life. Support for these OSs will be removed for all versions of Confluent Platform after the 7.8.x release. You should not use these OSs in a production deployment.
[2](1, 2) Java 11, 17 and 21 are supported. Java 8 is not supported on this operating system.
[3]Confluent Platform 7.7.x and later versions no longer support these operating systems because they have reached their end of life. Do not use these operating systems in a production deployment.

Additional notes about OS support:

SELinux

Confluent Platform is supported on AlmaLinux, Amazon Linux, Debian, RHEL, CentOS, Debian, Rocky Linux, and Ubuntu Operating Systems.

Confluent is not accountable for Security-Enhanced Linux (SELinux) policy development, support, or enforcement. If you experience issues running Confluent Platform with SELinux enabled on a supported Linux Operating System, contact your OS provider for assistance.

Windows
Windows is not currently supported for Confluent Platform. Windows 8.1 and later and Windows 2016 and later are supported by the C/C++ and .NET clients.
macOS
macOS 10.14 and later is supported for testing and development purposes only.
File descriptors
For the file descriptor requirement for Kafka, see File Descriptors and mmap.
ulimit
Control Center requires many open RocksDB files. Set the ulimit for the number of open files to a minimum value of 16384 using the ulimit -n command. For the other Confluent Platform components, specifically Schema Registry and Replicator, you can leave the ulimit as the OS default.
RHEL with TLS

When you install Confluent Platform on RHEL8 with TLS encryption, you must add DH Key Size JVM Parameters for each component. For more information, see Strong crypto defaults in RHEL 8 and deprecation of weak crypto algorithms.

Set the following component-level environment variables to the argument:

  • Schema Registry: SCHEMA_REGISTRY_OPTS=-Djdk.tls.ephemeralDHKeySize=2048
  • Kafka and Connect: KAFKA_OPTS=-Djdk.tls.ephemeralDHKeySize=2048
  • REST Proxy: KAFKAREST_OPTS=-Djdk.tls.ephemeralDHKeySize=2048
  • ksqlDB: KSQL_OPTS=-Djdk.tls.ephemeralDHKeySize=2048
atime

The atime mount option impacts performance, because every read operation on a file system causes a write operation.

Confluent recommends disabling the tracking of atime by setting the noatime option when you mount Kafka data disks.

Java

You need to separately install the correct version of Java before you start the Confluent Platform installation process.

The following table lists Java support in Confluent Platform by version. Note the following:

  • Java 8 was deprecated in Confluent Platform version 7.4.x and has been removed in a Confluent Platform 8.0.
  • Java 11 is now only supported for Kafka Streams and Kafka clients in Confluent Platform 8.0.x.
  • Ubuntu 22.04 and 24.04 operating systems support Java versions 21, 17 and 11, but do not support Java 8 in Confluent Platform 7.8.x or later.
  • The current Docker image supports Java 21. For more information, see Docker.
  • Eclipse Temurin (formerly known as AdoptOpenJDK), OpenJDK, Zulu OpenJDK, and Oracle are supported with Confluent Platform.
  • You should use the full JDK to help Confluent Support with troubleshooting and to provide better support if you experience issues with Confluent Platform.
Confluent Platform Recommended Supported
8.0.x 21 21, 17 *
7.9.x 17 17, 11, 8
7.8.x 17 17, 11, 8
7.7.x 17 17, 11, 8
7.6.x 17 17, 11, 8
7.5.x 17 17, 11, 8
7.4.x 17 17, 11, 8
7.3.x 17 17, 11, 8
7.2.x 11 11, 8

* Java 8 has been removed in Confluent Platform 8.0. Java 11 is only supported for Kafka Streams and Kafka clients.

From a security perspective, you should always use the latest released patch version because older versions may have security vulnerabilities.

Only long-term support (LTS) versions of Java are supported. For more information about Java versions, see Java Version History.

Scala

Confluent Platform Scala for Packages and Docker Scala for Maven JARs
8.0.x 2.13 2.13
7.9.x 2.13 2.12, 2.13
7.8.x 2.13 2.12, 2.13
7.7.x 2.13 2.12, 2.13
7.6.x 2.13 2.12, 2.13
7.5.x 2.13 2.12, 2.13
7.4.x 2.13 2.12, 2.13
7.3.x 2.13 2.12, 2.13
7.2.x 2.13 2.12, 2.13
7.1.x 2.13 2.12, 2.13

Confluent Platform for Apache Flink compatibility

The following tables list Confluent Platform for Apache Flink® compatibility and requirements.

Confluent Platform Confluent Manager for Apache Flink® Apache Flink® Apache Flink® Kubernetes Operator Release Date Standard End of Support Platinum End of Support
8.0.x 2.0.X 1.18.x, 1.19.x, 1.20.x 1.12.x June 24, 2025 June 24, 2027 June 24, 2028
7.9.x 1.1.x 1.18.x, 1.19.x, 1.20.x 1.10.x February 19, 2025 February 19, 2027 February 19, 2028
7.8.x 1.0.x 1.18.x, 1.19.x, 1.20.x 1.10.x December 2, 2024 December 2, 2026 December 2, 2027
7.7.x N/A 1.18.x, 1.19.x 1.8.x July 26, 2024 N/A July 26, 2027 for select customers only

Note the following:

  • Standard support means any support level below Platinum support. For example, if you have Gold support, you have Standard support.
  • The end of support date applies to minor versions and any maintenance versions that come after the minor version. This means that maintenance versions follow the same lifecycle of the minor version.

Confluent Platform for Apache Flink has the following operational requirements:

Apache Flink® version Confluent Platform versions Java versions Kubernetes version OpenShift version
1.20 7.8.x - 7.9.x 11, 17 1.26+ 4.12 and 4.14+
1.19 7.7.x - 7.9.x 11, 17 1.26+ 4.12 and 4.14+
1.18 7.7.x - 7.9.x 11, 17 1.26+ 4.12 and 4.14+

Confluent Control Center

You can use Confluent Control Center with compatible Confluent Platform versions.

The following sections show the compatibility between the new and legacy versions of Control Center and Confluent Platform.

The version of Control Center included with Confluent Platform version 7.9 and earlier is now considered legacy, but is supported for the versions listed. Starting with Confluent Platform version 8.0, Control Center (Legacy) has been discontinued and an improved Control Center is available. This new and improved Control Center is available as a separate download and is the recommended alternative to Control Center (Legacy).

Control Center

To install Control Center, see Confluent Control Center Installation.

Control Center Confluent Platform
2.2.0 7.7.x-8.0.x
2.0.0 through 2.1.0 7.5.x-7.9.x

For more information on the support policy for Control Center and version compatibility, see Control Center Support Policy.

Control Center (Legacy)

Control Center (Legacy) is the version of Control Center that is included with Confluent Platform 7.9 and earlier.

Control Center (Legacy) Confluent Platform Release Date EoL Date
Not supported 8.0.x and later June 11, 2025 Not supported
7.9.x 7.1.x through 7.9.x February 19, 2025 February 19, 2027
7.8.x 7.1.x through 7.8.x December 2, 2024 December 2, 2026
7.7.x 7.1.x through 7.7.x July 26, 2024 July 26, 2026
7.6.x 7.1.x through 7.6.x February 9, 2024 February 9, 2026
7.5.x 7.1.x through 7.5.x August 25, 2023 August 25, 2025
7.4.x 7.1.x through 7.4.x May 3, 2023 Expired
7.3.x 7.1.x through 7.3.x November 4, 2022 Expired
7.2.x 7.1.x through 7.2.x July 6, 2022 Expired
7.1.x 7.1.x April 5, 2022 Expired

Confluent CLI

You can use the Confluent CLI with compatible Confluent Platform versions.

Confluent Platform Confluent CLI
8.0.x 4.26.0 through most recent 4.x version
7.9.x 4.7.0 through most recent 4.x version
7.8.x 4.7.0 through most recent 4.x version
7.7.x 3.64.3 through most recent 3.x version
7.6.x 3.48.0 through most recent 3.x version
7.5.x 3.2.1 through most recent 3.x version
7.4.x 3.2.1 through most recent 3.x version
7.3.x 2.28.1 through most recent 2.x version
7.2.x 2.19.0 through most recent 2.x version
7.1.x 2.6.1 through most recent 2.x version

To install and use a later version of the CLI than the version that shipped with Confluent Platform, you must download and install the later version using these instructions.

ksqlDB

When you install Confluent Platform, you get a specific version of ksqlDB. The following table shows which version of ksqlDB ships with each version of Confluent Platform.

Confluent Platform ksqlDB Kafka Streams version
8.0.x 8.0.0 4.0.0
7.9.x 7.9.0 3.9.0
7.8.x 7.8.0 3.8.0
7.7.x 7.7.0 3.7.0
7.6.x 7.6.0-137 3.6.0
7.5.x 0.29.0 3.5.0
7.4.x 0.28.3-RC7 3.4.0
7.3.x 0.28.2 3.3.2
7.2.x 0.26.0 3.2.0
7.1.x 0.23.1 3.1.0

ZooKeeper

Important

As of Confluent Platform 8.0, ZooKeeper has been removed. You must use KRaft mode for metadata management. For steps to migrate from ZooKeeper to KRaft, see Migrate from ZooKeeper to KRaft on Confluent Platform. For links to ZooKeeper topics in older versions of the documentation, see ZooKeeper Topic Guide.

Confluent Platform Apache ZooKeeper™
8.0.x Not supported
7.9.x 3.8.4
7.8.x 3.8.4
7.7.x 3.5.6 through 3.8.4 (3.8.4 recommended)
7.6.x 3.5.6 through 3.8.3 (3.8.3 recommended)
7.5.x 3.5.6 through 3.8.3 (3.8.3 recommended)
7.4.x 3.4.10 through 3.8.3 (3.8.3 recommended)
7.3.x 3.4.10 through 3.8.3 (3.8.3 recommended)
7.2.x 3.4.10 through 3.8.3 (3.8.3 recommended)
7.1.x 3.4.10 through 3.8.3 (3.8.3 recommended)

Component security

Kafka

Security Feature Confluent Platform
Audit log Supported
Authentication with SASL/PLAIN Supported
Authentication with SASL/Kerberos and SASL/PLAIN Supported
Authentication with SASL/SCRAM Supported
Authentication with OAuth 2.0 Supported, versions 7.7.x and later
Authorization (Access control lists) Supported
TLS/SSL Wire Encryption Supported

Kafka Connect clients

Security Feature Confluent Platform
Authentication and Encryption with secured Kafka brokers Supported

Apache Kafka Streams clients

Security Feature Confluent Platform
Authentication and Encryption with secured Kafka brokers Supported

Confluent Control Center

Security Feature Confluent Platform
HTTPS Supported

Authentication and Encryption with secured Kafka brokers:

  • User login with HTTP Basic authentication
Supported
Single Sign-On (SSO) Supported 7.5.x and later

REST Proxy

Security Feature Confluent Platform
Authentication and Encryption with secured Kafka brokers Supported
HTTPS (SSL) for REST clients Supported

Schema Registry

Security Feature Confluent Platform
Access Control (RBAC) for Schema Linking Exporters Supported 7.0.9, 7.1.7, 7.2.5, 7.3.2, 7.3.3, 7.4.0, and later.
Authentication and Encryption with secured Kafka brokers Supported
HTTPS (SSL) for REST clients Supported

Clients

To learn more about features and details of supported clients, see Overview of Confluent Platform Client Programming.

Client System Requirements
.NET
  • Targets frameworks net451 and netstandard1.3.
  • Supported on the .NET Framework 4.5.1 and and .NET Core 1.0 and later.
  • Not supported on Mono.
C/C++
  • Build toolchain must support C99 and C++98 or later.
Golang
  • Golang 1.7 or later.
  • Build toolchain must support CGo and C99 or later.
  • Not supported on Windows.
Python
  • Python 2.7 or later.
  • Windows is supported.
Java
JavaScript
  • Node.js - any supported version.
  • Linux (X64 and ARM64) - both glibc and musl/Alpine.
  • macOS - ARM64/M1.
  • Windows - X64.

Connectors

A support lifecycle policy applies to Confluent Platform connectors and connector versions. For more information, see Support policy for self-managed connectors.

Cross-component compatibility

The following sections describe version compatibility between Kafka brokers and individual components.

Kafka Connect workers

Kafka Connect workers that are included in supported versions of Confluent Platform are compatible with any Kafka broker.

Kafka Java clients

Kafka Java Clients that are included in any supported version of Confluent Platform are compatible with any Kafka broker that is included in any supported version of Confluent Platform.

Note that versions may be compatible, but support is offered for a specific time window for each version. For a table of release and end of support dates for Java clients by version number, see Java client support.

Kafka Streams clients

See the Kafka Streams Compatibility Matrix for the version compatibility between Kafka Streams clients and Kafka brokers.

Auto data balancing

Compatible with Kafka brokers included in any supported version of Confluent Platform.

Confluent C, C++, Python, Go and .NET

All versions of Confluent’s non-Java clients are compatible with all versions of Confluent Platform. Note that although all versions are compatible, support is provided for a specific time window by version. For a table of release and end of support dates for librdkafka and derived clients by version number, see librdkafka and derived client support.

Schema Registry

Schema Registry that is included in supported versions of Confluent Platform is compatible with any Kafka broker that is included in supported Confluent Platform versions.

Replicator

For data transfer Replicator maintains the same compatibility matrix as Java clients, detailed in Kafka Java clients. However some Replicator features have different compatibility requirements:

  • Schema Translation requires that both source and destination clusters are running Confluent 5.2.0 or later.
  • Offset Translation requires that both source and destination clusters are running Confluent 5.1.0 or later.
  • Automatic topic creation and config sync requires that the destination cluster is at a later version than the source cluster.
  • The timestamp-interceptor for consumers supports only Java clients, as described in Configuring the consumer for failover (timestamp preservation).

REST Proxy

REST Proxy included in supported versions of Confluent Platform is compatible with any Kafka broker that is included in supported Confluent Platform versions.

Orchestration tools

Confluent for Kubernetes

For details about the supported Kubernetes environments, refer to Confluent for Kubernetes Supported Environments.

The following table summarizes the Confluent Platform features supported with Confluent for Kubernetes.

Confluent Platform 8.0 Feature Availability in CFK 3.00*
Kafka Broker Available, only via Confluent Server
Schema Registry Available
REST Proxy Available
ksqlDB Available
Connect Available
Control Center Available
Replicator Available
Security: Role-based Access Control Available [2]
Security: Authentication Available [3]
Security: Network Encryption Available
Structured Audit Logs Available [4]
MDS-based Access Control Lists (ACLs) Available
Secrets Protection Available [5]
Schema Validation Available
FIPS Available
Multi-region Clusters Available
Tiered Storage Available
Self-Balancing Clusters Available
Auto Data Balancer Use Self-Balancing Clusters
Confluent REST API Available
Cluster Registry Not Available
Cluster Linking Available
Health+ Available
  • [1] Confluent Control Center is a separate download. See Installation.
  • [2] Only available for new installations.
  • [3] Supports SASL/Plain and mTLS for Kafka authentication. Does not support Kerberos or SASL/Scram.
  • [4] Supported through Kafka configuration overrides. See Use Properties Files to Configure Audit Logs in Confluent Platform for the properties you need to set in config overrides. Does not support centrally managed Audit Logs.
  • [5] Kubernetes Secrets are integrated. CFK does not enable you to use Confluent Secret Protection.

Ansible Playbooks for Confluent Platform

Ansible Playbooks for Confluent Platform (Confluent Ansible) provides you a simple way to configure and deploy Confluent Platform on a traditional VM or bare metal infrastructure. For more information, see Ansible documentation .

For version compatibility among Confluent Ansible, Confluent Platform, Ansible, and Python, see Ansible Requirements.

The following table summarizes the Confluent Platform features supported with Ansible Playbooks for Confluent Platform.

Confluent Platform 8.0 Feature Availability in Ansible Playbooks for Confluent Platform 8.0
Kafka Broker Available
Schema Registry Available
REST Proxy Available
ksqlDB Available
Connect Available
Control Center Available [1]
Replicator Available [2]
Security: Authentication Available
Security: Role-based Access Control (RBAC) Available
Security: Network Encryption Available
Structured Audit Logs Available
MDS-based Access Control Lists (ACLs) Available [3]
Secrets Protection Available
Schema Validation Available
FIPS Available
Multi-region Clusters Available
Tiered Storage Available
Self-Balancing Clusters Available
Auto Data Balancer Not available
Confluent REST API Available
Health+ Available
Cluster Registry Available
Cluster Linking Available
  • [1] Confluent Control Center requires a separate installation. See Installation.
  • [2] Cannot have RBAC enabled on the source or target cluster.
  • [3] Only available for new installations. Does not support centrally managing ACLs across multiple Kafka clusters.

You can manually configure the features marked as Not available outside of the scope of Ansible Playbooks for Confluent Platform. If you take the hybrid installation approach, refer to the appropriate installation document in Confluent documentation to ensure your install path of mixing Ansible installation and manual installation is supported.

Docker

If you are not using a higher-level container orchestration system like Kubernetes, Confluent Platform Docker images are available for use directly with Docker. Docker version 1.11 or later running on a supported operating system is required to use the Docker images.

Release Docker Image Reference Operating System JDK Version Python Version Scala Version
8.0.x Docker Image Reference for Confluent Platform RHEL UBI 9 Temurin 21.0.7 3.9.21 2.13
7.9.x Docker Image Reference (7.9) RHEL UBI 8 Temurin 17.0.13 3.9.20 2.13
7.8.x Docker Image Reference (7.8) RHEL UBI 8 Temurin 17.0.12 3.9.20 2.13
7.7.x Docker Image Reference (7.7) RHEL UBI 8 Zulu OpenJDK 17.0.11 3.9.19 2.13
7.6.x Docker Image Reference (7.6) RHEL UBI 8 Zulu OpenJDK 11.0.21 3.9.18 2.13
7.5.x Docker Image Reference (7.5) RHEL UBI 8 Zulu OpenJDK 11.0.20 3.9.13 2.13
7.4.x Docker Image Reference (7.4) RHEL UBI 8 Zulu OpenJDK 11.0.18 3.9.13 2.13
7.3.x Docker Image Reference (7.3) RHEL UBI 8 Zulu OpenJDK 11.0.15-1 3.9.7 2.13
7.2.x Docker Image Reference (7.2) RHEL UBI 8 Zulu OpenJDK 11.0.15-1 3.6.8 2.13

MirrorMaker

MirrorMaker 2 is supported as a stand-alone executable, but is not supported as a connector.

The following Confluent products provide more complete solutions that handle data replication, topic configuration, and schemas to improve availability, scalability, and ease of use.

Web browsers

The following web browsers are supported by Confluent Control Center.

Browser Supported Version
Apple Safari Latest Stable
Google Chrome Latest Stable
Mozilla Firefox Latest Stable

VMWare

When you run Confluent Platform on VMWare, note the following:

  • You should enable compression to help mitigate the performance impacts while maintaining business continuity.
  • You should disable vMotion and disk snapshotting for Confluent Platform as the features could cause a full cluster outage when used with Kafka.

Confluent supports customers who choose to run Confluent Platform on VMWare VMotion. However, the scope of support will be limited to questions and fixes which are related to Confluent Platform itself and not troubleshooting or debugging VMotion (which is outside the scope of Confluent Support). For more information, see Running Confluent Platform on VMWare VMotion (requires sign in) on the Confluent Support portal and VMware optimization.