Chapter 9. Supported Configurations

The following platforms are tested for Streams for Apache Kafka 3.1 running with Kafka on the version of Red Hat Enterprise Linux (RHEL) stated.

Platforms 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.

Streams for Apache Kafka is designed for FIPS.

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.

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 tested with OpenJDK 17 and 21.

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

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

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.

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.