Release notes
Latest information about features and issues in this release
Abstract
Chapter 1. New and changed features Copy linkLink copied to clipboard!
Red Hat Service Interconnect is the Red Hat build of Skupper.
The following features are included in Red Hat Service Interconnect version 2.1:
- You can now redeem tokens in a local system site.
- You can now install the Network Observer using an operator.
-
CRD documentation - all resources now include documentation. For example, you can view details of a CR in OpenShift console or using
kubectl explain
. -
Removal of some CLI shortcuts, for example
-r
. You must now specify the full parameter, for example--routing-key
. -
You can now specify high availability when creating a site using the CLI. For example
skupper site create --enable-ha
. - Exposing services from other namespaces is now fully supported.
-
You can now install the controller (as a container) on local systems using the CLI command:
skupper system install
-
The CLI commands for
skupper system
have been refactored
Chapter 2. Long term support Copy linkLink copied to clipboard!
Red Hat Service Interconnect 1.8 is available as a long term support (LTS) release version.
See Red Hat Service Interconnect 1.8 documentation for more information.
Chapter 3. Supported configurations Copy linkLink copied to clipboard!
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
Red Hat Enterprise Linux 8 | Yes | Yes | Yes | |
Red Hat Enterprise Linux 9 | Yes | Yes | Yes | |
Red Hat Enterprise Linux 10 |
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 fall under commercially reasonable support.
Operator
The operator is supported with OpenShift 4.x only.
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
Red Hat Enterprise Linux 8 | Yes | Yes | Yes | |
Red Hat Enterprise Linux 9 | Yes | Yes | Yes |
Router
For use in Kubernetes sites and as a gateway for containers or machines.
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
Red Hat Enterprise Linux 8 | Yes | Yes | Yes | |
Red Hat Enterprise Linux 9 | Yes | Yes | Yes |
The Skupper router is not supported for standalone use as a messaging router.
3.1. Commercially reasonable support Copy linkLink copied to clipboard!
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
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.
Ingress types
- Gateway
- Contour
- Nginx (This requires configuration for TLS passthrough.)
- NodePort
Podman sites
Service Interconnect requires Podman version 4 or later.
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
Linux | Yes | Yes | Yes |
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.
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. Technology Preview features Copy linkLink copied to clipboard!
Some features in this release are currently in Technology Preview. This section describes the Technology Preview features in Red Hat Service Interconnect 2.1.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
- Certificate rotation
- You can now rotate certificates as described in README.
- Exposing pods by name
- You can create connectors using pod names to expose those pods on the application network.
Chapter 5. Upgrading sites Copy linkLink copied to clipboard!
To upgrade a site, you need to upgrade the controller using the same method you used to install the Red Hat Service Interconnect, that is, one of the following:
- Updating the operator
- Applying the latest YAML
-
For local systems
skupper system install
andskupper system reload
Chapter 6. Fixed issues Copy linkLink copied to clipboard!
See Red Hat Service Interconnect Resolved Issues for 2.1.x for a list of issues that have been fixed in this release.
Chapter 7. Known issues Copy linkLink copied to clipboard!
SKUPPER-2584 - Multiple Skupper Links
You can create multiple links from one site to another. However, the links do not perform as expected. For example, traffic flow across multiple links with different costs might not be as expected.
Workaround
To workaround this issue, make sure a link does not exist before creating a new link.
SKUPPER-2569 - Link cost is not updatable
If you create a link and later attempt to change the link cost, the update fails.
NoteThe
kubectl get link
command reports the updated link cost, however, that link cost does not affect traffic flow.Workaround
To workaround this issue, delete the link and create it again with the desired link cost.
Revised on 2025-10-03 09:26:45 UTC