Chapter 9. Supported Configurations


Supported configurations for Streams for Apache Kafka 3.1.

9.1. Supported platforms

Streams for Apache Kafka 3.1 is supported on all versions of Red Hat OpenShift Container Platform that are in Full or Maintenance support. For more information, see the following articles:

While support covers all current OpenShift versions, the following table lists the specific platform versions that were tested at the time of the Streams for Apache Kafka 3.1 release. Latest refers to the latest stable version available and tested at the time of the release.

Expand
PlatformVersionArchitecture

Red Hat OpenShift Container Platform

4.16–4.20 (tested); 4.12, 4.14 (supported)

x86_64, ppc64le (IBM Power), s390x (IBM Z and IBM® LinuxONE), aarch64 (64-bit ARM)

Red Hat OpenShift Container Platform disconnected environment

Latest

x86_64, ppc64le (IBM Power), s390x (IBM Z and IBM® LinuxONE), aarch64 (64-bit ARM)

Red Hat OpenShift Dedicated

Latest

x86_64

Microsoft Azure Red Hat OpenShift (ARO)

Latest

x86_64

Red Hat OpenShift Service on AWS (ROSA), including hosted control planes (HCP)

Latest

x86_64

Red Hat build of MicroShift

Latest

x86_64

Unsupported features:

  • Red Hat MicroShift does not support Kafka Connect’s build configuration for building container images with connectors.
  • IBM Z and IBM® LinuxONE s390x architecture does not support Streams for Apache Kafka OPA integration.

9.2. FIPS compliance

Streams for Apache Kafka is designed for FIPS. Streams for Apache Kafka container images are based on RHEL 9.2, which contains cryptographic modules submitted to NIST for approval.

To check which versions of RHEL are approved by the National Institute of Standards and Technology (NIST), see the Cryptographic Module Validation Program on the NIST website.

Red Hat OpenShift Container Platform is designed for FIPS. When running on RHEL or RHEL CoreOS booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries submitted to NIST for FIPS validation only on the x86_64, ppc64le (IBM Power), s390x (IBM Z), and aarch64 (64-bit ARM) architectures. For more information about the NIST validation program, see Cryptographic Module Validation Program. For the latest NIST status for the individual versions of the RHEL cryptographic libraries submitted for validation, see Compliance Activities and Government Standards.

9.3. Supported clients

Only client libraries built by Red Hat are supported for Streams for Apache Kafka. Currently, Streams for Apache Kafka only provides a Java client library, which is tested and supported on kafka-clients-4.0.0.redhat-00013 and newer. Clients are supported for use with Streams for Apache Kafka 3.1 on the following operating systems and architectures:

Expand
Operating SystemArchitectureJVM

RHEL and UBI 8, 9, and 10

x86, amd64, ppc64le (IBM Power), s390x (IBM Z and IBM® LinuxONE), aarch64 (64-bit ARM)

Java 17 and 21

Clients are tested with OpenJDK 17 and 21. RHEL 10 is supported on Java 21 only. The IBM JDK is supported but not regularly tested against during each release.

Support for Red Hat Universal Base Image (UBI) versions correspond to the same RHEL version.

9.4. Supported Apache Kafka ecosystem

In Streams for Apache Kafka, only the following components released directly from the Apache Software Foundation are supported:

  • Apache Kafka Broker
  • Apache Kafka Connect
  • Apache MirrorMaker 2
  • Apache Kafka Java Producer, Consumer, Management clients, and Kafka Streams
Note

Apache ZooKeeper is supported solely as an implementation detail of Apache Kafka and should not be modified for other purposes.

9.5. Additional supported features

  • Kafka Bridge
  • Drain Cleaner
  • Cruise Control
  • Distributed Tracing
  • Streams for Apache Kafka Console
  • Streams for Apache Kafka Proxy

See also, Chapter 11, Supported integration with Red Hat products.

9.6. Console supported browsers

Streams for Apache Kafka Console is supported on the most recent stable releases of Firefox, Edge, Chrome and Webkit-based browsers.

9.7. Subscription limits and core usage

Cores used by Red Hat components and product operators do not count against subscription limits. Additionally, cores or vCPUs allocated to KRaft controller-only nodes or ZooKeeper nodes are excluded from subscription compliance calculations and do not count towards a subscription.

9.8. Storage requirements

Streams for Apache Kafka has been tested with block storage and is compatible with the XFS and ext4 file systems, which are commonly used with Kafka. File-based storage options, such as NFS, are not tested or supported for primary broker storage and may cause instability or degraded performance.

Kafka tiered storage is supported as an optional capability. For the remote storage tier, AWS S3 and NFS-backed storage are tested and supported. Other S3-compatible or cloud-based object storage systems might also work, but they have not been tested. If using an untested storage backend, evaluate performance and compatibility in your environment before using it in production.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top