이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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.

맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat