Red Hat build of Quarkus Supported Configurations

Red Hat build of Quarkus is tested and verified with Red Hat OpenShift Container Platform, Red Hat Enterprise Linux, and Microsoft® Windows Server. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments. [1]

• Red Hat build of Quarkus 3.2.x
• Red Hat build of Quarkus 2.13.x

Red Hat build of Quarkus 3.2.x

Red Hat build of Quarkus 3.2.x Supported Configurations

In order to be running in a supported configuration, Red Hat build of Quarkus must be running in one of the following JVMs and operating systems.

Red Hat build of Quarkus applications that are compiled to a native executable using the Red Hat Build of Quarkus Native builder 23.0 Java 17 for AMD64 container are covered under Production Support on following operating systems.

Red Hat build of Quarkus applications that are compiled to a native executable using the Red Hat Build of Quarkus Native builder 23.0 Java 17 for ARM64 container are covered under Development Support on following operating systems.

Red Hat build of Quarkus 3.2.x Tested Configurations

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

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

Red Hat build of Quarkus 3.2.x Serverless tested configuration

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

NOTE: Red Hat OpenShift Serverless does currently not support ARM(aarch64)

Red Hat build of Quarkus 3.2.x Integrations

Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each Red Hat build of Quarkus release. This list of tested integrations may expand over time.

Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.

The following databases were tested as part of the Red Hat build of Quarkus 3.2.x release. [3]

Red Hat build of Quarkus 2.13.x

Red Hat build of Quarkus 2.13.x Supported Configurations

In order to be running in a supported configuration, Red Hat build of Quarkus must be running in one of the following JVMs and operating systems.

Red Hat build of Quarkus applications that are compiled to a native executable using the Red Hat Build of Quarkus Native builder 22.3 Java 17 container are supported on following operating systems.

Red Hat build of Quarkus 2.13.x Tested Configurations

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

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

Red Hat build of Quarkus 2.13.x Serverless tested configuration

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

Red Hat build of Quarkus 2.13.x Integrations

Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each Red Hat build of Quarkus release. This list of tested integrations may expand over time.

Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.

The following databases were tested as part of the Red Hat build of Quarkus 2.13.x release. [3]

[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, database driver, etc., or its version is not 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 OpenJDK builds from Red Hat. For more information on Open JDK on Windows please see this article.

[3] Red Hat build of Quarkus provides a Bill Of Material (BOM), which states the database driver version to use. Only the database extension and the driver is supported as part of the Quarkus subscription, not the database server.

[4] Red Hat build of Quarkus support for System Z and Power Systems is limited to Red Hat OpenShift Container Platform.

[5] The Red Hat Build of Quarkus Native builder container is default used when building a Red Hat build of Quarkus application using ./mvnw -Pnative -Dquarkus.native.container-build=true and it is not supported to use in source-to-image (s2i) builds.

[6] The Red Hat build of Quarkus is supported on Red Hat OpenShift Container platform as specified here.

[7] It's supported to use a Java runtime from Adoptium.net, but support is limited to issues in Quarkus and does not include any native issues or issues related to another Kubernetes distribution than OpenShift.

[8] Support is limited to the Linux and Windows distributions supported by the Eclipse Adoptium distribution

[9] ARM (Aarch64) has been tested as part of this release. See the release notes for known issue in regards to Aarch64.