Release Notes for Red Hat build of Quarkus 1.7

Red Hat build of Quarkus 1.7


This document contains release notes for Red Hat build of Quarkus 1.7.


These release notes list new features, features in technology preview, known issues, and issues fixed in Red Hat build of Quarkus 1.7.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Red Hat build of Quarkus

Red Hat build of Quarkus is a Kubernetes-native Java stack that is optimized for use with containers and Red Hat OpenShift Container Platform. Quarkus is designed to work with popular Java standards, frameworks, and libraries such as Eclipse MicroProfile, Apache Kafka, RESTEasy (JAX-RS), Hibernate ORM (JPA), Spring, Infinispan, and Apache Camel.

The Quarkus dependency injection solution is based on CDI (contexts and dependency injection) and includes an extension framework to expand functionality and to configure, boot, and integrate a framework into your application.

Quarkus provides a container-first approach to building Java applications. This approach makes it much easier to build microservices-based applications written in Java as well as enabling those applications to invoke functions running on serverless computing frameworks. For this reason, Quarkus applications have small memory footprints and fast startup times.

Chapter 2. New and changed features

This section provides an overview of new features and changes introduced in Red Hat build of Quarkus 1.7.6.

2.1. gRPC Quarkus extension

The quarkus-grpc extension introduces the following capabilities:

  • Ability for Quarkus application to consume and expose gRPC services.
  • Support based on the Quarkus reactive core as well as imperative (blocking) consumption.
  • Support for plain-text and TLS communication, both relying on HTTP/2 transport.
  • Support for TLS encryption and mutual authentication.
  • Implementation of the gRPC health and reflection services. Health is integrated with the quarkus-smallrye-health extension and the reflection service makes it easier to use tools such as grpcurl.

2.2. Quarkus native mode

This release provides full support for running a Quarkus application as a native application when compiled using the Red Hat build of Quarkus Native build container. Running a Quarkus application as a native application instead of a Java application can greatly improve startup times and memory utilization. This feature was Tech preview in the previous version of Red Hat build of Quarkus.

2.3. OpenShift Serverless Serving in native and JVM mode

Running a Quarkus application in OpenShift Serverless (Serving) is now fully supported in both JVM and native mode. The quarkus-openshift extension additionally supports deploying a JVM applications to OpenShift Container Platforms with Serverless Serving installed using the Apache Maven.

2.4. Support for client to connect to Red Hat Data Grid

With the quarkus-infinispan-client extension the client can connect to a server running outside of application processes.

The Infinispan client Quarkus extension provides the following features:

  • Creation of native image
  • Automatic injection of important resources such as RemoteCache (named), RemoteCacheManger, CounterManager
  • User based ProtoStream Marshalling
  • Indexed and non-indexed querying
  • Continuous query
  • Near cache
  • Authentication and authorization
  • Encryption
  • Counters

2.5. Spring compatibility layers

Expanded support for new Spring compatibility layers including:

  • quarkus-spring-cache
  • quarkus-spring-cloud-config-client
  • quarkus-spring-scheduled

Chapter 3. Red Hat build of Quarkus supported platforms, configurations, extensions, and dependencies

3.1. Supported extensions and dependencies

For a list of Red Hat build of Quarkus extensions and dependencies that Red Hat supports for use in production environments see the Red Hat build of Quarkus Component Details page (login required).

3.2. Development support

Red Hat provides development support for the following Red Hat build of Quarkus features, plug-ins, extensions, and dependencies:


  • Live development mode
  • Remote development mode


  • protobuf-maven-plugin

Extensions and dependencies

Chapter 4. Deprecated components and features

The components and features listed in this section are deprecated with Red Hat build of Quarkus 1.7. They are included and supported in this release, however no enhancements will be made to these components and features and they might be removed in the future.

  • The quarkus-smallrye-opentracing extension
  • The use of ReactiveX APIs

Chapter 5. Technology preview

This section lists features and extensions that are in Technology Preview in Red Hat build of Quarkus 1.7.


These features are for Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information on Red Hat Technology Preview features, see Technology Preview Features Scope.

Extensions and dependencies

  • For a list of Red Hat build of Quarkus extensions and dependencies that Red Hat provides as Technology Preview with Red Hat build of Quarkus 1.7.6 see the Red Hat build of Quarkus Component Details page (login required).

Chapter 6. Known issues

This section lists known issues with Red Hat build of Quarkus 1.7.

  • Issue #11633 Missing zero-config solution for OpenShift Serverless. This issue affects only deployment of Quarkus native Serverless applications
  • QUARKUS-451 Increased instability in NativeAggregatorIT in kafka-streams-quickstart
  • QUARKUS-688 Cannot deploy mutable-jar (used by remote development feature) on OpenShift

Chapter 7. Fixed issues in Quarkus 1.7.5 SP1

Quarkus 1.7.5 SP1 contains the following bug fix:

Chapter 8. Fixed issues in Quarkus 1.7.6 GA

Quarkus 1.7.6 GA contains the following bug fixes:

8.4. Component version upgrades

  • QUARKUS-543: Upgrade Hibernate Validator version to 6.1.6.Final
  • QUARKUS-548: Upgrade Quarkus HTTP version to 3.0.15.Final
  • QUARKUS-606: Upgrade Eclipse Vert.x components to version 3.9.5
  • QUARKUS-625: Update Apache HTTP Client to version 4.5.13
  • QUARKUS-685: Update Infinispan version to 11.0.4 and Infinispan ProtoStream version to 4.3.4.Final

Revised on 2021-01-11 16:32:07 UTC

Legal Notice

Copyright © 2021 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.