Chapter 3. Supported configurations


Expand
Table 3.1. Red Hat Enterprise Linux CLI (using dnf)
 x86-64aarch64s390xppc64le

Red Hat Enterprise Linux 8

Yes

Yes

Yes

Yes

Red Hat Enterprise Linux 9

Yes

Yes

Yes

Yes

Red Hat Enterprise Linux 10

    

Kubernetes sites (primary support)

Service Interconnect 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:

Support for Non-OpenShift distributions of Kubernetes requires Kubernetes version 1.28 or later.

Ingress types (primary support)

  • LoadBalancer
  • OpenShift Routes (supported only on OpenShift)

Other ingress types fall under commercially reasonable support.

Expand
Table 3.2. Red Hat Enterprise Linux Podman sites (primary support)
 x86-64aarch64s390xppc64le

Red Hat Enterprise Linux 8

Yes

Yes

Yes

Yes

Red Hat Enterprise Linux 9

Yes

Yes

Yes

Yes

Expand
Table 3.3. Router (primary support)
 x86-64aarch64s390xppc64le

Red Hat Enterprise Linux 8

Yes

Yes

Yes

Yes

Red Hat Enterprise Linux 9

Yes

Yes

Yes

Yes

For use in Kubernetes and local system sites.

Note

The Skupper router is not supported for standalone use as a messaging router.

Expand
Table 3.4. CLI (binary download)
 x86-64aarch64s390xppc64le

Linux

Yes

Yes

Yes

Yes

Mac

Yes

   

Windows

Yes

   

Kubernetes distributions (commercially reasonable support)

Red Hat will provide assistance running Service Interconnect on any CNCF-certified distribution of Kubernetes. Note, however, that our testing is done on OpenShift.

https://www.cncf.io/certification/software-conformance/#logos

Kubernetes Ingress types (commercially reasonable support)

  • Gateway
  • Contour
  • Nginx (This requires configuration for TLS passthrough.)
  • NodePort
Expand
Table 3.5. Podman sites (commercially reasonable support)
 x86-64aarch64s390xppc64le

Linux

Yes

Yes

Yes

Yes

Service Interconnect requires Podman version 4 or later.

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, Red Hat recommends upgrading all sites to the latest version.

Disconnected operation

Red Hat supports deployment of Service Interconnect in disconnected environments.

Note

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.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

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.

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 Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top