Chapter 3. Supported configurations
Command-line interface
- Red Hat Enterprise Linux 8 x86-64 and aarch64
- Red Hat Enterprise Linux 9 x86-64 and aarch64
- Linux x86-64 and aarch64
- macOS x86-64
- Windows x86-64
Router
For use in Kubernetes-based sites and as a gateway for containers or machines.
- Red Hat Enterprise Linux 8 x86-64 and aarch64
- Red Hat Enterprise Linux 9 x86-64 and aarch64
Red Hat Service Interconnect is not supported for standalone use as a messaging router.
Red Hat Service Interconnect Operator
The operator is supported with OpenShift 4.x only.
OpenShift versions
- OpenShift 3.11
- OpenShift 4.12, 4.13, 4.14, 4.15 and 4.16
- ROSA and ARO
- OpenShift Container Platform and OpenShift Dedicated
Installing Red Hat Service Interconnect in a disconnected network by mirroring the required components to the cluster is supported.
Ingress types
- LoadBalancer
- OpenShift Routes
CPU architecture
- x86-64 and aarch64
Kubernetes distributions
Red Hat provides assistance running Red Hat Service Interconnect on any CNCF-certified distribution of Kubernetes.
Note, however, that Red Hat Service Interconnect is tested only on OpenShift.
Ingress types
- Contour
- Nginx - This requires configuration for TLS passthrough
- NodePort
Upgrades
Red Hat supports upgrades from one downstream minor version to the next, with no jumps. While Red Hat aims to have compatibility across minor versions, we recommend upgrading all sites to latest version.
If you have applications that require long lived connections, for example Kafka clients, consider using a load balancer as ingress instead of a proxy ingress such as OpenShift route. If you use an OpenShift route as ingress, expect interruptions whenever routes are configured.
For information about the latest release, see Red Hat Service Interconnect Supported Configurations.
