Chapter 3. Fuse on OpenShift
Fuse on OpenShift enables you to deploy Fuse applications on OpenShift Container Platform.
3.1. Supported version of OpenShift
For details of the supported version (or versions) of OpenShift Container Platform to use with Fuse on OpenShift, see the Supported Configurations page.
3.2. Supported images
Fuse on OpenShift provides the following Docker-formatted images:
Image | Platform | Supported architectures |
---|---|---|
| Spring Boot | AMD64 and Intel 64 (x86_64) |
| Spring Boot | AMD64 and Intel 64 (x86_64) |
| Spring Boot |
IBM Z and LinuxONE (s390x) |
| Apache Karaf | AMD64 and Intel 64 (x86_64) |
| Apache Karaf | AMD64 and Intel 64 (x86_64) |
| Red Hat JBoss Enterprise Application Platform | AMD64 and Intel 64 (x86_64) |
| Red Hat JBoss Enterprise Application Platform | AMD64 and Intel 64 (x86_64) |
| Fuse console |
AMD64 and Intel 64 (x86_64) |
| Fuse console operator |
AMD64 and Intel 64 (x86_64) |
| Apicurito REST application generator | AMD64 and Intel 64 (x86_64) |
| Apicurito REST API editor | AMD64 and Intel 64 (x86_64) |
| API Designer Operator | AMD64 and Intel 64 (x86_64) |
3.3. New features in Fuse 7.11 on OpenShift
Fuse on OpenShift provides following new features in version 7.11:
Fuse Console performance tuning (OpenShift 4.x only)
You can tune the performance of the Fuse Console by setting any of the
clientBodyBufferSize
,proxyBuffers
, andsubrequestOutputBufferSize
environment variables.Note: This feature is not supported on OpenShift 3.11.
Support for JDK 11
Fuse 7.11 offers support for building the Fuse on OpenShift quickstarts using JDK 11.
Running quickstarts with
openshift-maven-plugin
Fuse 7.11 uses new
openshift-maven-plugin
when building and running the Fuse on OpenShift quickstarts with Maven archtypes.Support for IBM Power Systems, IBM Z, and LinuxONE
Fuse 7.11 adds support for IBM Power Systems(ppc64le), IBM Z, and LinuxONE (s390x) on Red Hat OpenShift Container Platform 4.9 and later.
NoteIn Fuse 7.11, installing the Fuse on OpenShift imagestreams and templates on IBM Power Systems, IBM Z, and LinuxONE is not supported. Only the components that can be installed with Fuse on OpenShift Operators are supported on IBM Power Systems, IBM Z, and LinuxONE.
3.4. Important notes
Important notes for the Fuse 7.11 release of the Fuse on OpenShift distribution:
- Support for Fuse 7.11 on OpenShift Container Platform (OCP) 4.9 or later
- Fuse 7.11 contains updates that enable it to work with OpenShift Container Platform (OCP) 4.9 or later. If you plan to upgrade to OCP 4.10, you must upgrade Fuse to version 7.11 before you upgrade OCP to version 4.10. Earlier versions of Fuse (prior to 7.10) do not support OCP 4.9 or later.
- Data Virtualization has been removed
- Data Virtualization is deprecated since Fuse 7.7 and has been removed from Fuse 7.8.
- Spring Boot 1 is has been removed
- Spring Boot 1 is deprecated since Fuse 7.7 and has been removed from Fuse 7.8. We recommend that you migrate your Spring Boot applications to Spring Boot 2, following the guidance in the Spring Boot 2.0 Migration Guide.
- Fabric8 Maven plugin is removed
- Fabric8 Maven plugin is completely removed from Fuse 7.10 and replaced with OpenShift Maven plugin since Fuse 7.10. Use OpenShift Maven plugin to build and deploy your applications.
- Running quickstarts with JDK11
- Use the correct JDK11 profile during the compile time if you want to use JDK11 based image at runtime. When building and deploying the quickstarts using JDK11, ensure that you have installed JDK11 on your build machine and then build your quickstarts using the correct JDK11 profile.
- Changes in spring-boot artifact Id
-
In Fuse 7.11, Spring Boot is upgraded to 2.5.13. In this new version
spring-cloud-starter-kubernetes-config
artifact id is changed tospring-cloud-starter-kubernetes-client-config
.
Quickstart Spring-Boot RHOSAK fails because of spring-boot upgrade
- The
eap-camel-jpa
quickstart has been removed -
The
eap-camel-jpa
quickstart has been removed from Fuse 7.8 due to an issue with a dependency. - Jolokia not externally accessible since Fuse 7.8
- Starting in Fuse 7.8, Jolokia default protocol is switched from HTTP to HTTPS.
- FIPS-enabled Jolokia agent becomes unavailable
- In OCP FIPS-enabled Jolokia agent becomes unavailable due to unsupported security encoding.