Chapter 3. Supported configurations


Expand
Table 3.1. CLI
 x86-64aarch64s390xppc64le

Red Hat Enterprise Linux 8

Yes

Yes

Yes

 

Red Hat Enterprise Linux 9

Yes

Yes

Yes

 

Kubernetes sites

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

  • LoadBalancer
  • OpenShift Routes (supported only on OpenShift)

Other ingress types for non-OpenShift distributions of Kubernetes fall under commercially reasonable support.

Operator

The operator is supported with OpenShift 4.x only.

Expand
Table 3.2. Podman sites
 x86-64aarch64s390xppc64le

Red Hat Enterprise Linux 8

Yes

Yes

Yes

 

Red Hat Enterprise Linux 9

Yes

Yes

Yes

 

Router

For use in Kubernetes sites and local system sites (Podman, Docker, Linux).

Expand
 x86-64aarch64s390xppc64le

Red Hat Enterprise Linux 8

Yes

Yes

Yes

 

Red Hat Enterprise Linux 9

Yes

Yes

Yes

 
Note

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

Expand
Table 3.3. CLI
 x86-64aarch64s390xppc64le

Linux

Yes

Yes

Yes

 

Mac

Yes

   

Windows

Yes

   

Distributions

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

Ingress types

  • Gateway
  • Contour
  • Nginx (This requires configuration for TLS passthrough.)
  • NodePort

Podman sites

Service Interconnect requires Podman version 4 or later.

Expand
 x86-64aarch64s390xppc64le

Linux

Yes

Yes

  

Router

The router has commercially reasonable support when run as a container on Linux.

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.

Port negotiation limitation

If your protocol negotiates the communication port, for example active FTP, you cannot use that protocol to communicate across a service network.

Back to top
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

© 2025 Red Hat