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:
- Declarative
- This release provides better support for using YAML to create network resources to allow communication across the hybrid cloud.
- Updating configuration
- In version 2, you can change site configuration without recreating sites.
- Exposing services
- You can now determine precisely where services are exposed on the application network.
- Local systems
- In addition to Podman, Docker and Linux sites are now supported.
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!
3.1. Primary support Copy linkLink copied to clipboard!
3.1.1. CLI Copy linkLink copied to clipboard!
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
RHEL 8 | Yes | Yes | Yes | |
RHEL 9 | Yes | Yes | Yes |
3.1.2. Kubernetes sites Copy linkLink copied to clipboard!
3.1.2.1. Distributions Copy linkLink copied to clipboard!
Supported | Tested | |
---|---|---|
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 Copy linkLink copied to clipboard!
- 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 Copy linkLink copied to clipboard!
The operator is supported with OpenShift 4.x only.
3.1.3. Podman sites Copy linkLink copied to clipboard!
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
RHEL 8 | Yes | Yes | Yes | |
RHEL 9 | Yes | Yes | Yes |
3.1.4. Router Copy linkLink copied to clipboard!
For use in Kubernetes sites and as a gateway for containers or machines.
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
RHEL 8 | Yes | Yes | Yes | |
RHEL 9 | Yes | Yes | Yes |
The Skupper router is not supported for standalone use as a messaging router.
3.2. Commercially reasonable support Copy linkLink copied to clipboard!
3.2.1. CLI Copy linkLink copied to clipboard!
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
Linux | Yes | Yes | Yes | |
Mac | Yes | |||
Windows | Yes |
3.2.2. Kubernetes sites Copy linkLink copied to clipboard!
3.2.2.1. Distributions Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
- Gateway
- Contour
- Nginx (This requires configuration for TLS passthrough.)
- NodePort
3.2.3. Podman sites Copy linkLink copied to clipboard!
Service Interconnect requires Podman version 4 or later.
x86-64 | aarch64 | s390x | ppc64le | |
---|---|---|---|---|
Linux | Yes | Yes |
3.2.4. Router Copy linkLink copied to clipboard!
The router has commercially reasonable support when run as a container on Linux.
3.3. Upgrades Copy linkLink copied to clipboard!
- 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 Copy linkLink copied to clipboard!
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.0.
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.
- CLI
- You can use the Skupper CLI to create sites, link sites and expose services on Kubernetes and local systems.
- Local system sites
- You can create Podman, Docker and Linux sites and link those sites to your application network, however these sites are technology preview for support purposes.
- Exposing pods by name
- You can create connectors using pod names to expose those pods on the application network.
- Exposing services from other namespaces
-
You can expose services, for example, deployments, from namespaces other than the site namespace. This feature uses the
AttachedConnector
resource. - Network observer
- You can deploy the Network observer to provide the Network console and an API to monitor the application network.
Chapter 5. Upgrading sites Copy linkLink copied to clipboard!
This release of Red Hat Service Interconnect is not compatible with previous versions of Red Hat Service Interconnect. To upgrade, delete your sites and recreate them using Red Hat Service Interconnect 2.0.
Chapter 6. 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.
SKUPPER-2561 - Orphan connector references
If you use automation to create a namespace, site and connector resources, you might want to delete the namespace and run your automation again with a new namespace that has the same name. In this scenario, some of the connector resources might still exist and report errors.
Workaround
To workaround this issue, consider one of the following:
- Allow extra time after namespace deletion.
- Use a random prefix when creating namespace.
SKUPPER-869 - Enable idle connection timeouts for the TCP transport
If an endpoint is terminated, for example a client is killed, the other endpoint observes a half-closed connection. If the other endpoint does not close the connection or attempt to send data to the connection, the Skupper router does not release the memory allocated to that connection
Workaround
Avoid client server configurations that use this behavior if possible. For example, if a server automatically closes dormant connections, or attempts to communicate with client, the Skupper router frees the memory when a client is terminated.
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-04-28 13:58:50 UTC