Este contenido no está disponible en el idioma seleccionado.

Chapter 3. Supported configurations


3.1. Primary support

3.1.1. CLI

Expand
 x86-64aarch64s390xppc64le

RHEL 8

Yes

Yes

Yes

 

RHEL 9

Yes

Yes

Yes

 

3.1.2. Kubernetes sites

3.1.2.1. Distributions

Expand
 SupportedTested

OpenShift 4.x (OCP)

Yes

Yes

OpenShift on AWS (ROSA)

  

OpenShift on Google Cloud (OSD)

  

OpenShift on IBM Cloud (RHOIC)

  

OpenShift on Microsoft Azure (ARO)

  

Amazon EKS

  

Azure AKS

  

Google GKE

  

OpenShift 4.x support includes the latest release and latest EUS release.

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

3.1.2.2. Ingress types

  • LoadBalancer
  • OpenShift Routes (supported only on OpenShift)

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

3.1.2.3. Operator

The operator is supported with OpenShift 4.x only.

3.1.3. Podman sites

Expand
 x86-64aarch64s390xppc64le

RHEL 8

Yes

Yes

Yes

 

RHEL 9

Yes

Yes

Yes

 

3.1.4. Router

For use in Kubernetes sites and as a gateway for containers or machines.

Expand
 x86-64aarch64s390xppc64le

RHEL 8

Yes

Yes

Yes

 

RHEL 9

Yes

Yes

Yes

 
Note

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

3.2. Commercially reasonable support

3.2.1. CLI

Expand
 x86-64aarch64s390xppc64le

Linux

Yes

Yes

Yes

 

Mac

Yes

   

Windows

Yes

   

3.2.2. Kubernetes sites

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

3.2.2.2. Ingress types

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

3.2.3. Podman sites

Service Interconnect requires Podman version 4 or later.

Expand
 x86-64aarch64s390xppc64le

Linux

Yes

Yes

  

3.2.4. Router

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

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

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

Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat