이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 10. Supported Configurations
Supported configurations for the Streams for Apache Kafka 2.9 release.
10.1. Supported platforms 링크 복사링크가 클립보드에 복사되었습니다!
The following platforms are tested for Streams for Apache Kafka 2.9 running with Kafka on the version of Red Hat Enterprise Linux (RHEL) stated.
| Operating System | Architecture | JVM |
|---|---|---|
| RHEL 8, 9, and 10 | x86, amd64, ppc64le (IBM Power), s390x (IBM Z and IBM® LinuxONE), aarch64 (64-bit ARM) | Java 11 (deprecated) and Java 17 |
Platforms are tested with Open JDK 11 and 17, though Java 11 is deprecated in Streams for Apache Kafka 2.7 and will be removed in version 3.0. The IBM JDK is supported but not regularly tested against during each release. Oracle JDK 11 is not supported.
FIPS compliance
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.
10.2. 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-3.8.0.redhat-00007 and newer.
Clients are tested with Open JDK 11 and 17.
10.3. 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
- Apache MirrorMaker 2
- Apache Kafka Java Producer, Consumer, Management clients, and Kafka Streams
- Apache ZooKeeper
Apache ZooKeeper is supported solely as an implementation detail of Apache Kafka and should not be modified for other purposes.
10.4. Additional supported features 링크 복사링크가 클립보드에 복사되었습니다!
- Kafka Bridge
- Cruise Control
- Distributed Tracing
See also, Chapter 12, Supported integration with Red Hat products.
10.5. 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 ZooKeeper nodes are excluded from subscription compliance calculations and do not count towards a subscription.
10.6. 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.