Red Hat build of Apache Camel 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]

Red Hat build of Apache Camel 4.0 for Quarkus 3 GA

Red Hat build of Apache Camel for Quarkus is tested and verified with:

Red Hat build of Apache Camel 4.0 for Quarkus 3 Supported Native Build Configuration

Camel Quarkus applications that are compiled to a native executable using the Red Hat Build of Quarkus Native builder are also supported on all the listed supported platforms in the Red Hat build of Apache Camel 4, only on OpenJDK 17 and Red Hat Universal Base Image 8 Minimal.

Camel Quarkus applications compiled to a native executable must be built using the following builder image:

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

Red Hat build of Apache Camel 4.0 for Quarkus 3 Supported Messaging Providers

The following messaging providers were tested with Red Hat build of Apache Camel 4 for Quarkus 3:

Broker Tested version Supported version Messaging client version
Red Hat AMQ Broker 7.11.x 7.x quarkus-qpid-jms 2.4.0
Red Hat AMQ Streams 2.4.x 2.x kafka-clients 3.4.0
IBM Websphere MQ* 9.3.2 9.x 9.3.2

Note: Support for IBM Websphere MQ is in JVM mode only by configuring camel-quarkus-jms to use the listed WebSphere MQ JMS client. Please refer to the IBM Websphere MQ documentation regarding supported client and broker combinations.

Note: Red Hat tests messaging providers using the messaging driver versions shown above. These drivers are typically compatible with a range of message broker versions. See your vendor’s documentation for information about driver compatibility with specific server versions.


Red Hat build of Apache Camel 4.0 for Quarkus 3 Supported Database Integrations

The following databases were tested with Red Hat build of Apache Camel 4 for Quarkus:

Database Tested versions JDBC Driver
PostgreSQL 13.2 JDBC Postgresql Driver 42.5.0
MySQL 8.0, 5.7 MySQL Connector 8.0.30
MariaDB 10.3, 10.6 MariaDB Java Client 3.0.8
Microsoft SQLServer Linux 2017, 2019-CU10 MS SQL Server JDBC Driver 11.2.0 JRE 11
Oracle 19c, 19c-RAC Oracle JDBC Driver 21.5.0.0
DB2 11.5 IBM Data Server Driver for JDBC and SQLJ 11.5.7.0
MongoDB 5.0 -


Note Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are typically compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.

Support Policy for Cloud Database Usage on Application Services Products

Camel Extensions for Quarkus 2.13 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.13

Camel Extensions for Quarkus 2.13 Supported Platforms

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

JVM Operating System / Platform Version Chipset Architecture Container image
OpenJDK 11, 17 [2], TemurinJDK 11, 17 Red Hat Enterprise Linux 8 x86_64
OpenJDK 11, 17 [2] Red Hat OpenShift Container Platform 4.10, 4.11, 4.12, 4.13, 4.14 x86_64 ubi8/openjdk-11, ubi8/openjdk-17
OpenJDK 11, 17 [2] Red Hat OpenShift Service on AWS (ROSA) 4.10, 4.11, 4.12, 4.13, 4.14 x86_64 ubi8/openjdk-11, ubi8/openjdk-17
OpenJDK 11, 17 [2] Microsoft Azure Red Hat OpenShift (ARO) 4.10, 4.11 x86_64 ubi8/openjdk-11, ubi8/openjdk-17
OpenJDK 11, 17 [2], TemurinJDK 11, 17 Other [3] x86_64


Camel Quarkus applications that are compiled to a native executable using the Red Hat Build of Quarkus Native builder are also supported on all the platforms above, only on OpenJDK 17 and Red Hat Universal Base Image 8 Minimal.

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 22.3

Camel Extensions for Quarkus 2.13 Supported Messaging Providers

The following messaging providers were tested with Camel Extensions for Quarkus:

Broker Tested version Supported version
Red Hat AMQ Broker 7.10.x 7.x
Red Hat AMQ Streams 2.2.x, 2.4.x 2.x


Red Hat AMQ Broker was tested using the quarkus-qpid-jms client.

Camel Extensions for Quarkus 2.13 Supported Database Integrations

The following databases were tested with Camel Extensions for Quarkus:

Database Tested versions JDBC Driver
PostgreSQL 13.2 JDBC Postgresql Driver 42.5.0
MySQL 8.0, 5.7 MySQL Connector 8.0.30
MariaDB 10.3, 10.6 MariaDB Java Client 3.0.8
Microsoft SQLServer Linux 2017, 2019-CU10 MS SQL Server JDBC Driver 11.2.0 JRE 11
Oracle 19c, 19c-RAC, 21 Oracle JDBC Driver 21.5.0.0
DB2 11.5 IBM Data Server Driver for JDBC and SQLJ 11.5.7.0
MongoDB 5.0 -


Note Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are typically compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.

Support Policy for Cloud Database Usage on Application Services Products

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
OpenJDK 11 [2] Red Hat OpenShift Service on AWS (ROSA) x86_64 4.11
OpenJDK 11 [2] Microsoft Azure Red Hat OpenShift (ARO) x86_64 4.10


Support Guidelines for Red Hat Application Foundation Products Deployed in 3rd-party Environments

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
Red Hat OpenShift Service on AWS (ROSA) x86_64 4.11
Microsoft Azure Red Hat OpenShift (ARO) x86_64 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 OpenShift Service on AWS (ROSA) 4.11 x86_64 Red Hat OpenJDK 11 (ubi8/openjdk-11) [2]
Microsoft Azure Red Hat OpenShift (ARO) 4.10 x86_64 Red Hat OpenJDK 11 (ubi8/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] Support guidelines

Comments