Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 3. Supported configurations
| 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
| 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.
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.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}