Overview
Key features and supported configurations
Abstract
Chapter 1. Key features Copy linkLink copied to clipboard!
Red Hat Service Interconnect is a Red Hat build of the open source Skupper project. Skupper introduces a service network, linking services across the hybrid cloud.
A service network enables communication between services running in different network locations. It allows geographically distributed services to connect as if they were all running in the same site.
The following are key features of Skupper:
- Private to public site connectivity: You expose only specific services and ports to a remote site.
-
Minimal effort: A few
skupperCLI commands to expose services from one site to another. - Security: mTLS for all cross site communication.
- Load balancing and failover of services.
Chapter 2. Supported standards and protocols Copy linkLink copied to clipboard!
Red Hat Service Interconnect supports the following TLS versions for site links:
- TLS 1.2
- TLS 1.3
Chapter 3. Supported configurations Copy linkLink copied to clipboard!
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
- IBM Z and IBM LinuxONE (s390x)
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
- IBM Z and IBM LinuxONE (s390x) for containers.
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.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, aarch64, and s390x
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.
Appendix A. About Service Interconnect documentation Copy linkLink copied to clipboard!
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Revised on 2025-02-24 19:05:05 UTC