Introduction
Key features and supported configurations
Abstract
Chapter 1. Key features
Red Hat Service Interconnect is a Red Hat build of the open source Content from skupper.io is not included.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
Red Hat Service Interconnect supports the following TLS versions for site links:
- TLS 1.2
- TLS 1.3
Chapter 3. Supported configurations
Command-line interface
- RHEL 8 x86-64
- RHEL 9 x86-64
Router
For use in Kubernetes-based sites and as a gateway for containers or machines.
- RHEL 8 x86-64
- RHEL 9 x86-64
Note: RHSI is not supported for standalone use as a messaging router.
RHSI Operator
The operator is supported with OpenShift 4.x only.
OpenShift versions
- OpenShift 3.11
- OpenShift 4.10, 4.11 and 4.12
- ROSA and ARO
- OpenShift Container Platform and OpenShift Dedicated
Installing RHSI in a disconnected network by mirroring the required components to the cluster is supported.
Ingress types
- LoadBalancer
- OpenShift Routes
CPU architecture
- x86-64
Podman sites:
Podman-based sites are a Technical Preview feature.
You can create Podman sites only on OS versions where the Skupper CLI and router are supported.
Kubernetes distributions
Red Hat provides assistance running Red Hat Service Interconnect on any Content from www.cncf.io is not included.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.
Chapter 4. Resources
The following resources are available:
- Content from skupper.io is not included.Skupper - Getting started
- Content from skupper.io is not included.Skupper - Examples
Content from skupper.io is not included.Skupper - Using the Skupper CLI
- Content from skupper.io is not included.Creating a site using the CLI
- Content from skupper.io is not included.Custom sites
- Content from skupper.io is not included.Linking sites
- Content from skupper.io is not included.Specifying link cost
- Content from skupper.io is not included.Exposing services on the service network from a namespace
- Content from skupper.io is not included.Exposing services on the service network from a local machine
- Content from skupper.io is not included.Exploring a service network
- Content from skupper.io is not included.Securing a service network
- Content from skupper.io is not included.Supported standards and protocols
- Content from skupper.io is not included.CLI options for working with different clusters
Content from skupper.io is not included.Skupper - Using Skupper podman
Content from skupper.io is not included.Skupper - Using the Skupper console
Content from skupper.io is not included.Skupper - Configuring Skupper sites using YAML
- Content from skupper.io is not included.Creating a Skupper site using YAML
- Content from skupper.io is not included.Linking sites using YAML
- Content from skupper.io is not included.Configuring services using annotations
- Content from skupper.io is not included.Appendix A: Site ConfigMap YAML reference
Content from skupper.io is not included.Skupper - Troubleshooting a service network
- Content from skupper.io is not included.Checking sites
- Content from skupper.io is not included.Checking links
- Content from skupper.io is not included.Checking gateways
- Content from skupper.io is not included.Creating a Skupper debug tar file
- Content from skupper.io is not included.Improving Skupper router performance
- Content from skupper.io is not included.Resolving common problems
Content from skupper.io is not included.Skupper - Securing a service network using policies
- Content from skupper.io is not included.About the policy system
- Content from skupper.io is not included.Upgrading on a cluster with existing sites
- Content from skupper.io is not included.Creating policies for the policy system
- Content from skupper.io is not included.Exploring the current policies for a cluster
- Content from skupper.io is not included.Creating a site using the Skupper Operator
Appendix A. About Service Interconnect documentation
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 2024-04-25 14:57:27 UTC