Camel Extensions for Quarkus Supported Configurations

Updated -

Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement.[1]

Camel Extensions for Quarkus 2.7 GA

Camel Extensions for Quarkus is tested and verified with:

  • Red Hat OpenShift Container Platform (OCP)
  • Red Hat Enterprise Linux (RHEL)
  • Red Hat Build of Quarkus 2.7

Camel Extensions for Quarkus 2.7 Supported Platforms

In order to be running in a supported configuration, Camel Extensions for Quarkus must be running on one of the following JVMs and operating systems:

JVM Operating System / Platform Chipset Architecture Version
OpenJDK 11 [2] Red Hat Enterprise Linux x86_64 8
OpenJDK 11 [2] Red Hat OpenShift Container Platform x86_64 4.6, 4.7, 4.8, 4.9, 4.10

Camel Quarkus applications that are compiled to a native executable using the Red Hat Build of Quarkus Native builder are supported on the following operating systems:

Operating System Chipset Architecture Version
Red Hat Enterprise Linux x86_64 8
Red Hat OpenShift Container Platform x86_64 4.6, 4.7, 4.8, 4.9, 4.10

Camel Extensions for Quarkus 2.7 Tested Configurations

A full range of platform tests have been performed on the following tested configurations using JVM mode:

Operating System / Platform Chipset Architecture Container image
OpenShift 4.6, 4.10 x86_64 Red Hat OpenJDK 11 [2]
Red Hat Enterprise Linux 8.5 x86_64 OpenJDK 11 [2]

A full range of platform tests have been performed on the following tested configurations using native mode:

Operating System / Platform Chipset Architecture Container image
OpenShift 4.6, 4.10 x86_64 Red Hat Universal Base Image 8 Minimal
Red Hat Enterprise Linux 8.5 x86_64 N/A

Camel Quarkus Supported Native Build Configuration

Red Hat build of Quarkus compiled to a native application must be built using the following builder image:

Builder Image Chipset Architecture Version/Tag
Red Hat Build of Quarkus Native builder x86_64 21.3

Camel Extensions for Quarkus 2.7 Supported Database Integrations

The following databases were tested with Camel Extensions for Quarkus:

Database Versions
PostgreSQL 13.2
MySQL 8.0, 5.7
MariaDB 10.6
Microsoft SQLServer Linux 2019-CU10
Oracle 19, 18.4
DB2 11.5
MongoDB 5.0

Camel Extensions for Quarkus 2.2 GA

Camel Extensions for Quarkus is tested and verified with:

  • Red Hat OpenShift Container Platform (OCP)
  • Red Hat Enterprise Linux (RHEL)
  • Red Hat Build of Quarkus 2.2

Camel Extensions for Quarkus 2.2 Supported Platforms

In order to be running in a supported configuration, Camel Extensions for Quarkus must be running on one of the following JVMs and operating systems:

JVM Operating System / Platform Chipset Architecture
OpenJDK 11 [2] Red Hat Enterprise Linux x86_64
OpenJDK 11 [2] Red Hat OpenShift Container Platform x86_64

Camel Quarkus applications that are compiled to a native executable using the Red Hat Build of Quarkus Native builder are supported on the following operating systems:

Operating System Chipset Architecture
Red Hat Enterprise Linux x86_64
Red Hat OpenShift Container Platform x86_64

Camel Extensions for Quarkus 2.2 Tested Configurations

A full range of platform tests have been performed on the following tested configurations using JVM mode:

Operating System / Platform Chipset Architecture Container image
OpenShift 4.6, 4.9 x86_64 Red Hat OpenJDK 11 [2]
Red Hat Enterprise Linux 8.5 x86_64 OpenJDK 11 [2]

A full range of platform tests have been performed on the following tested configurations using native mode:

Operating System / Platform Chipset Architecture Container image
OpenShift 4.6, 4.9 x86_64 Red Hat Universal Base Image 8 Minimal
Red Hat Enterprise Linux 8.5 x86_64 N/A

Camel Quarkus Supported Native Build Configuration

Red Hat build of Quarkus compiled to a native application must be built using the following builder image:

Builder Image Chipset Architecture Version/Tag
Red Hat Build of Quarkus Native builder x86_64 21.3

Camel Extensions for Quarkus 2.2 Supported Database Integrations

The following databases were tested with Camel Extensions for Quarkus:

Database Versions
PostgreSQL 13.2
MySQL 8.0, 5.7
MariaDB 10.3
Microsoft SQLServer Linux 2019-CU10
Oracle 18.4
DB2 11.5

[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.

[2] Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows

3 Comments

Hi, is there no supported Messaging/JMS integration for quarkus/camel-quarkus? I'd expect that Red Hat AMQ (Artemis) is supported for use with "camel-quarkus-jms".

I'm wondering why "quarkus-artemis-jms" is not part of core quarkus anymore, but moved to quarkiverse?!?

We need a whole supported configuration for quarkus, camel-quarkus with AMQ to be able to migrate from FUSE (on EAP) to quarkus.

Many thanks for your valuable feedback Jochen. Please allow me a day or two to follow up internally and come back with an answer.

Hello Jochen,

You definitely identified a gap in the supported components for Quarkus. We will be working on adding more JMS client support in the upcoming release of Camel Extensions for Quarkus. Since you also have a few support cases open, we can also move the discussion there.

Best Regards, Torsten Mielke